policy_status

Inspect policy mode, migration state, rules, budgets, approvals, and ledger integrity. Use when diagnosing whether an installation is in compatibility, observation, or enforcement mode.

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/policy-status.md

WHAT IT DOES

What policy_status does on Claude Flow

AI agents call policy_status to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why policy_status is rated Low

This tool queries and retrieves policy configuration, enforcement modes, and audit ledger data. While it accesses sensitive governance information (budgets, approvals, ledger state), it performs no data modification, deletion, or external execution. The medium severity reflects that policy and budget visibility could inform social engineering or privilege escalation, but the tool itself is read-only.

From the tool's definition Tool name 'policy_status' and description 'Inspect policy mode, migration state, rules, budgets, approvals, and ledger integrity' indicates retrieval and querying of system state without modification or deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs policy_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For policy_status, this is the rule to start with:

policy_status Allowed

policy_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "policy_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every policy_status call is checked against it from then on.

FAQ

Questions about policy_status

What does the policy_status tool do? +

Inspect policy mode, migration state, rules, budgets, approvals, and ledger integrity. Use when diagnosing whether an installation is in compatibility, observation, or enforcement mode. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on policy_status? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for policy_status: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Claude Flow. Nothing to install.

What risk level is policy_status? +

policy_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit policy_status? +

Yes. Add a rate_limit block to the policy_status rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block policy_status completely? +

Set action: deny in the PolicyLayer policy for policy_status. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides policy_status? +

policy_status is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →