{"version":"2.1.261","anchor":"artifact-copy-from-action-now-honors-denyask-permission-r","canonical_anchor":"artifact-copy-from-action-now-honors-denyask-permission-r","heading":"Artifact copy_from action now honors deny\/ask permission rules","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/artifact-copy-from-action-now-honors-denyask-permission-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Artifact `copy_from` action now honors deny\/ask permission rules\n\nCopying assets between artifacts now respects deny\/ask permission rules, not just prior consent.\n\nCopying assets between artifacts via `action: \"copy_from\"` now consults the permission-rule engine for deny and ask rules before proceeding, instead of only checking consent\/session state as before. A matching deny rule blocks the copy with a message naming the rule's tool and pattern, and a matching ask rule forces a confirmation prompt even if the destination or source was already consented.\n\nReading an artifact's structured page data (`read_page_data`) is now also checked against this permission-rule engine before fetching. Previously a session-wide \"Read artifacts' structured page data for the rest of this session\" grant auto-allowed all such reads; now a matching ask rule shows a one-shot confirmation instead, and a matching deny rule refuses the read entirely.\n\n- Area: Permissions\n- Names: `copy_from`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}