{"version":"2.1.261","anchor":"per-url-askdeny-rules-for-artifact-reads-page-data-reads","canonical_anchor":"per-url-askdeny-rules-for-artifact-reads-page-data-reads","heading":"Per-URL ask\/deny rules for artifact reads, page-data reads, diagnostics, and database reads","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/per-url-askdeny-rules-for-artifact-reads-page-data-reads","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Per-URL ask\/deny rules for artifact reads, page-data reads, diagnostics, and database reads\n\nArtifact reads, diagnostics, and database reads now check per-URL deny\/ask rules before falling back to session consent.\n\nArtifact tool permission checks gain a new rule-matching step that checks configured deny\/ask rules against the specific artifact URL before falling back to session-wide consent. This covers the `read_page_data`, `verify` (diagnostics), `read`, and `read_db` actions, and permission messages now surface which rule matched, for example when Claude wants to read the structured page data of an artifact.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}