Critical Risk →

freeze_account

Freeze (block) a Dock account. Pix outflows and card spend are halted but balance is preserved. Used for fraud holds, KYC re-verification, or judicial blocks.

How to control freeze_account ↓

What freeze_account does on Mcp Afip

AI agents call freeze_account to permanently remove resources in Mcp Afip — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why freeze_account needs a policy

Freezing an account halts all financial operations (payments, card spend) for the account holder. While the balance is preserved (not deleted), the action is effectively irreversible in its impact until manually reversed, disrupting the user's ability to transact. It falls closer to Destructive than Write due to the significant, hard-to-undo operational impact.

From the tool's definition Freeze (block) a Dock account. Pix outflows and card spend are halted

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

How to control freeze_account

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 freeze_account:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "freeze_account"
  ]
}

freeze_account disappears from the agent's tool list entirely, and any attempt to call it is denied. 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.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about freeze_account

What does the freeze_account tool do? +

Freeze (block) a Dock account. Pix outflows and card spend are halted but balance is preserved. Used for fraud holds, KYC re-verification, or judicial blocks. It is categorised as a Destructive tool in the Mcp Afip MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on freeze_account? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for freeze_account: 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 freeze_account? +

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

Can I rate-limit freeze_account? +

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

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

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