pay_merchant_clp
Pay a Chilean merchant in CLP via bank transfer. The user will receive a Telegram link to confirm the payment in their bank app. Use this for purchases at Chilean stores and services.
This record as markdown: /tools/agentpay/pay-merchant-clp.md
What pay_merchant_clp does on Agentpay
AI agents use pay_merchant_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. 15000 for $15,000 CLP) |
context | string | — | Why the agent is making this purchase |
merchant_name | string | Yes | Merchant name (e.g. 'Yaneken', 'Falabella') |
Parameters from the server's own tool schema.
Why pay_merchant_clp is rated Critical
This tool initiates bank transfers that debit funds from user accounts. It involves irreversible monetary transactions, making it the most severe category (Financial > Destructive > Execute > Write > Read). The critical severity reflects that an AI agent misusing this could drain accounts by making unauthorized payments to arbitrary merchants.
From the tool's definition Tool description explicitly states 'Pay a Chilean merchant in CLP via bank transfer' and 'for purchases at Chilean stores and services'. This directly moves money and commits financial obligations.
Attacks that exploit this kind of access
The rule that runs pay_merchant_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_merchant_clp, this is the rule to start with:
Any call to pay_merchant_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_merchant_clp call is checked against it from then on.
Questions about pay_merchant_clp
Pay a Chilean merchant in CLP via bank transfer. The user will receive a Telegram link to confirm the payment in their bank app. Use this for purchases at Chilean stores and services. 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_merchant_clp accepts 3 parameters: amount, context, merchant_name. Required: amount, merchant_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_merchant_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_merchant_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_merchant_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_merchant_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_merchant_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