Make an HTTP request and automatically pay if the server requires x402 payment. Returns the response body as a string.
AI agents use agenti_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 (cryptocurrency payments) based on server requirements. The 'automatically pay' language indicates the tool will execute transfers without requiring additional confirmation per transaction, creating critical risk if an AI agent is manipulated into calling this tool.
From the tool's definition Tool description states 'automatically pay if the server requires x402 payment' and server description indicates the tool enables LLM clients to 'spend' cryptocurrency.
Documented attack patterns abuse exactly the kind of access agenti_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 agenti_pay:
{
"version": "1",
"default": "deny",
"tools": {
"agenti_pay": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to agenti_pay is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Make an HTTP request and automatically pay if the server requires x402 payment. Returns the response body as a string. 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 agenti_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.
agenti_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 agenti_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 agenti_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.
agenti_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.