MCP Tool Scope & Revocation Auditor — OpenChainGraph compute node (compliance_mandate). Runs deterministically in-browser; zero PII, zero egress. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-151-agent-obo-mandate-validator. Open at: https://ainumbers.co/chai...
AI agents call audit_mcp_tool_scope_revocation to retrieve information from Ainumbers Mcp Apps without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
compute | string | — | Compute mode (v0.4 Compute Binding). "auto" (default) = server for gpu:false nodes with registered kernels; "server" = force server-side; "browser" = always ret |
parent_hashes | array | — | execution_hash values from upstream ChainGraph AP2 artifacts to chain from (sets chain.parent_hashes in the export). |
parent_tool_ids | array | — | tool_id values matching parent_hashes, in the same order. |
policy_parameters | object | — | Input parameters for this tool's decision function. For gpu:false nodes with a registered kernel, these are computed server-side when compute is "auto" or "serv |
Parameters from the server's own tool schema.
The tool performs compliance auditing and scope analysis (reading/querying MCP tool configurations) and generates audit artifacts for downstream validation. It retrieves and reports on tool scope and revocation status without modifying systems, executing arbitrary code, or moving funds. The execution hash export is for traceability, not financial value.
From the tool's definition Tool is described as an 'Auditor' that 'Runs deterministically in-browser; zero PII, zero egress.' It 'Exports an AP2 artifact' and feeds output to a validator. These are read-only audit and reporting operations.
Attacks that exploit this kind of access
MCP Tool Scope & Revocation Auditor — OpenChainGraph compute node (compliance_mandate). Runs deterministically in-browser; zero PII, zero egress. Exports an AP2 artifact with execution_hash for chain provenance. Output feeds: art-151-agent-obo-mandate-validator. Open at: https://ainumbers.co/chaingraph/art-150-mcp-tool-scope-revocation-auditor.html. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
audit_mcp_tool_scope_revocation accepts 4 parameters: compute, parent_hashes, parent_tool_ids, policy_parameters. The full parameter table on this page comes from the server's own tool schema.
Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for audit_mcp_tool_scope_revocation: 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 Ainumbers Mcp Apps. Nothing to install.
audit_mcp_tool_scope_revocation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the audit_mcp_tool_scope_revocation 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.
Set action: deny in the PolicyLayer policy for audit_mcp_tool_scope_revocation. 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.
audit_mcp_tool_scope_revocation is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →