Critical Risk →

request_withdraw

Request a bank withdrawal (saque) from a sub-account. Endpoint: POST /accounts/:id/request_withdraw

How to control request_withdraw ↓

What request_withdraw does on Mcp Afip

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

Critical Risk

Why request_withdraw needs a policy

This tool directly initiates financial transactions by requesting withdrawal of funds from a bank account. It commits financial obligations and moves money, which is the defining characteristic of the Financial category. The critical severity reflects that unauthorized withdrawals could result in direct monetary loss. High confidence due to explicit mention of 'withdrawal' and 'bank' in the description.

From the tool's definition Tool name 'request_withdraw' and description 'Request a bank withdrawal (saque) from a sub-account' explicitly indicate moving money from a financial account.

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

How to control request_withdraw

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

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

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

  1. Create a free account and register Mcp Afip — 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 request_withdraw

What does the request_withdraw tool do? +

Request a bank withdrawal (saque) from a sub-account. Endpoint: POST /accounts/:id/request_withdraw. It is categorised as a Financial tool in the Mcp Afip MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on request_withdraw? +

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

What risk level is request_withdraw? +

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

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

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

request_withdraw is provided by the Mcp Afip MCP server (codespar/mcp-dev-latam). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Afip tool call.

Start from Mcp Afip, 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 Afip 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.