pay

Pay for an HTTP resource — automatically handles 402 Payment Required (x402 protocol)

SERVERAgenti SOURCEnirholas/agenti

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-agenti/pay.md

WHAT IT DOES

What pay does on Agenti

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.

RISK

Why pay is rated Critical

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...

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pay safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay, this is the rule to start with:

pay Approval-gated

Any call to pay is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pay": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every pay call is checked against it from then on.

FAQ

Questions about pay

What does the pay tool do? +

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.

How do I enforce a policy on pay? +

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.

What risk level is pay? +

pay is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pay? +

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.

How do I block pay completely? +

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.

What MCP server provides pay? +

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.

KEEP EXPLORING

More on Agenti, and thousands of servers like it.

This server

All 73 Agenti tools → Critical-risk tools on this server →

Across the catalogue

pay_x402 on 8004swap →pay_invoice on Bitcoin MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →