What is access-policies?

Access rules that allow or deny add-in features for everyone or only under specified conditions, such as a document label.

Use it to disable features globally, restrict them for documents with particular Microsoft Purview sensitivity labels, or allow them only for approved documents.

A simple disabled-feature list can only switch features off globally. These rules let administrators apply restrictions to particular documents and explain where each restriction came from.

access-policies — Command for Claude Code by anthropics

About the project

Claude for Financial Services is a collection of agents, skills, commands, plugins, and data connectors for investment banking, equity research, private equity, and wealth-management workflows. Financial professionals use it to draft models, memos, research notes, and reconciliations for review by qualified people. The catalogue contains components from these workflows, including agents, skills, plugins, commands, and instructions.

anthropics/financial-services · 41,180 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/anthropics/financial-services

Made for: Claude Code.

Or install claude-for-msft-365-install, the plugin that ships this one along with the rest of its 1 skill, 9 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anthropics/financial-services/access-policies/github.svg)](https://agentmods.dev/commands/anthropics/financial-services/access-policies)

Your own site

<a href="https://agentmods.dev/commands/anthropics/financial-services/access-policies"><img src="https://agentmods.dev/badge/commands/anthropics/financial-services/access-policies/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anthropics/financial-services/access-policies"><img src="https://agentmods.dev/badge/commands/anthropics/financial-services/access-policies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,951 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00020	$0.02951
Opus 5.5	$0.00008	$0.01180
Sonnet 5.5	$0.00004	$0.00590
Haiku 4.5	$0.00002	$0.00295

Measured 1mo ago against content hash 0e6b8bf8ad2b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

access-policies scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-for-msft-365-install/commands/access-policies.md · 271 lines

How it starts

The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configure access_policies

access_policies is the add-in's access-control mechanism going forward: a JSON list of allow/deny statements — IAM-shaped — that decide which features are available and under what conditions. Where disabled_features is a single flat list — a feature is on or off for everyone — access_policies gives you the same off switch plus conditions and effects:

Want	`disabled_features`	`access_policies`
Turn a feature off for everyone	✔ `disabled_features='skills.authoring'`	✔ a resource-less `deny` statement (same effect)
Turn a feature off only on certain documents	✗	✔ add a `resource` (e.g. a sensitivity label)
Turn a feature off except for approved documents (allowlist)	✗	✔ `"effect": "allow"`
Attribute the block in UI copy / telemetry	limited	✔ per-statement `description` and source

A statement with no resource is exactly disabled_features — so anything you'd put there, you can put here. The resource is what adds granularity, and its type is the extension point: today the resource is a document (open_file, uploaded_file) identified by its Microsoft Purview sensitivity label or, for the open document, by its file path; further resource types plug into the same shape without a new config key. New deployments should start here; disabled_features remains supported for the simple flat case.

Two document-conditioned controls ship today:

Whether the add-in runs at all on an open document (the addin.access kill switch), keyed off the open document's label or its path.
Whether a file may be attached as an upload (file.upload), keyed off the attached file's own label — Office files and PDFs.

Walk the admin through the four steps below, then hand the finished JSON to manifest as one more key.

1. Get the label GUIDs

Skip this step if every rule matches on a file path (step 2) rather than a label.

Statements match on the label's GUID (mip_label_guid) — stable across renames and locales. Have the admin pull their taxonomy once with the Purview compliance PowerShell module (no app registration needed; it uses Microsoft's first-party sign-in):

Read the full file on GitHub · 271 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · +45 lines 0e6b8bf8ad2b
2mo ago First seen · 226 lines · 20 tokens per session scan A 48de8d8f1eb0

Subscribe to this mod's changes

access-policies is a command published in the GitHub repository anthropics/financial-services (41,180 stars, last pushed 13d ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,951 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.