AI agents use allowance_create to commit financial operations through Run402 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates a financial allowance on a blockchain network (Base Sepolia testnet) and generates a private key controlling an Ethereum address. Even though it's a testnet, the tool pattern and server context ('paid by X402', sibling tools like 'allowance_export') indicate this is part of a financial infrastructure.
From the tool's definition Create a new local agent allowance (Base Sepolia testnet). Generates a private key and derives the Ethereum address.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create a new local agent allowance (Base Sepolia testnet). Generates a private key and derives the Ethereum address. Saved to ~/.config/run402/allowance.json. It is categorised as a Financial tool in the Run402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for allowance_create: 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_create is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the allowance_create 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_create. 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_create 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 →