Pay for and acquire a $402 token. This debits the agent
AI agents use path402_acquire to commit financial operations through Path402 — Tokenised Web Content for AI Agents — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool explicitly performs a payment operation ('Pay for') and debits the agent's account to acquire a token. This directly moves funds/financial value, placing it firmly in the Financial category with critical severity since an AI agent misusing this tool could repeatedly spend funds autonomously.
From the tool's definition "Pay for and acquire a $402 token. This debits the agent"
Attacks that exploit this kind of access
Pay for and acquire a $402 token. This debits the agent. It is categorised as a Financial tool in the Path402 — Tokenised Web Content for AI Agents MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Path402 — Tokenised Web Content for AI Agents MCP server in PolicyLayer and add a rule for path402_acquire: 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 Path402 — Tokenised Web Content for AI Agents. Nothing to install.
path402_acquire 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 path402_acquire 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 path402_acquire. 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.
path402_acquire is provided by the Path402 — Tokenised Web Content for AI Agents MCP server (path402). 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 →