pay_person_clp
Send a CLP bank transfer to a person in Chile. The user will approve via Telegram. Use this for paying people (e.g. household help, freelancers, splitting bills).
This record as markdown: /tools/agentpay/pay-person-clp.md
What pay_person_clp does on Agentpay
AI agents use pay_person_clp to commit financial operations through Agentpay, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
amount | number | Yes | Amount in CLP (integer, e.g. 45000 for $45,000 CLP) |
context | string | — | What the payment is for |
recipient_rut | string | — | Recipient's RUT (Chilean tax ID) |
recipient_name | string | Yes | Recipient's name |
recipient_account | string | — | Recipient's bank account number |
Parameters from the server's own tool schema.
Why pay_person_clp is rated Critical
This tool moves money from one account to another (bank transfer in Chilean pesos). Even with user approval via Telegram, an AI agent with access to this tool could be manipulated into initiating unauthorized payments to arbitrary recipients. The financial impact is direct and irreversible. This is the most severe category of risk.
From the tool's definition Tool name contains 'pay', description states 'Send a CLP bank transfer' and 'paying people'. Server description indicates 'payment tools for AI agents'. This is explicitly a financial transaction mechanism.
Attacks that exploit this kind of access
The rule that runs pay_person_clp safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentpay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pay_person_clp, this is the rule to start with:
Any call to pay_person_clp is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentpay, apply this rule, and every pay_person_clp call is checked against it from then on.
Questions about pay_person_clp
Send a CLP bank transfer to a person in Chile. The user will approve via Telegram. Use this for paying people (e.g. household help, freelancers, splitting bills). It is categorised as a Financial tool in the Agentpay MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
pay_person_clp accepts 5 parameters: amount, context, recipient_rut, recipient_name, recipient_account. Required: amount, recipient_name. The full parameter table on this page comes from the server's own tool schema.
Register the Agentpay MCP server in PolicyLayer and add a rule for pay_person_clp: 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 Agentpay. Nothing to install.
pay_person_clp 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_person_clp 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_person_clp. 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_person_clp is provided by the Agentpay MCP server (agentpay-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentpay, and thousands of servers like it.
Across the catalogue