Pay for an HTTP resource — automatically handles 402 Payment Required (x402 protocol)
AI agents use pay to commit financial operations through Agenti — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool commits financial obligations by enabling automatic cryptocurrency payments. It moves money without explicit transaction-by-transaction human approval (the 'autonomously' design pattern of the server means an LLM agent could invoke this repeatedly). This is the most severe risk category—Financial—because it directly results in loss of monetary value.
From the tool's definition The tool name is 'pay' and its description explicitly states it 'Pay for an HTTP resource — automatically handles 402 Payment Required (x402 protocol)'. The server description confirms the agenti server 'Enables any MCP-compatible LLM client to autonomously...
Documented attack patterns abuse exactly the kind of access pay gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for pay:
{
"version": "1",
"default": "deny",
"tools": {
"pay": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to pay is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Pay for an HTTP resource — automatically handles 402 Payment Required (x402 protocol). It is categorised as a Financial tool in the Agenti MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Agenti MCP server in PolicyLayer and add a rule for pay: 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 Agenti. Nothing to install.
pay 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 pay 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 pay. 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.
pay is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.