AI agents call allowance_status to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of an agent's allowance (address, network, funding) and reports it back. No data is created, modified, deleted, or overwritten. No code is executed, and no financial transactions are initiated. It is purely informational retrieval, fitting the Read category.
From the tool's definition 'Check local agent allowance status' — retrieves status information about address, network, and funding without modifying data. The verb 'check' and the absence of any modification language ('create', 'update', 'delete') confirm read-only behavior.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Check local agent allowance status — address, network, and funding status. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for allowance_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 Run402. Nothing to install.
allowance_status 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 allowance_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.
Set action: deny in the PolicyLayer policy for allowance_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.
allowance_status is provided by the Run402 MCP server (kychee-com/run402). 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 →