Critical Risk →

schedule_payment

Schedule a future-dated payment (Pix, boleto, arrecadação, or TED). Itaú executes the debit on the scheduled date at D+0 cut-off.

How to control schedule_payment ↓

What schedule_payment does on Mcp Ap2

AI agents use schedule_payment to commit financial operations through Mcp Ap2 — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why schedule_payment needs a policy

This tool directly initiates a financial payment transaction via multiple payment methods (Pix, boleto, TED). It commits a real monetary debit from an account on the scheduled date. Misuse could result in unauthorized fund transfers, making it critical severity under the Financial category.

From the tool's definition 'Schedule a future-dated payment (Pix, boleto, arrecadação, or TED). Itaú executes the debit on the scheduled date at D+0 cut-off.'

Documented attack patterns abuse exactly the kind of access schedule_payment gives an agent:

How to control schedule_payment

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for schedule_payment:

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

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

  1. Create a free account and register Mcp Ap2 — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about schedule_payment

What does the schedule_payment tool do? +

Schedule a future-dated payment (Pix, boleto, arrecadação, or TED). Itaú executes the debit on the scheduled date at D+0 cut-off. It is categorised as a Financial tool in the Mcp Ap2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on schedule_payment? +

Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for schedule_payment: 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 Mcp Ap2. Nothing to install.

What risk level is schedule_payment? +

schedule_payment 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 schedule_payment? +

Yes. Add a rate_limit block to the schedule_payment 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 schedule_payment completely? +

Set action: deny in the PolicyLayer policy for schedule_payment. 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 schedule_payment? +

schedule_payment is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Ap2 tool call.

Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.