// MCP TOOL REFERENCE

retry_transaction

Retry a failed, expired, or rejected workflow execution. Creates a new workflow execution on the same account, optionally re-using the original workflow definition and customer references.

ServerMcp Afip
CategoryExecute

How to control retry_transaction ↓

WHAT IT DOES

What retry_transaction does on Mcp Afip

AI agents invoke retry_transaction to trigger actions in Mcp Afip. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

THE RISK

High Risk

Why retry_transaction needs a policy

This tool re-executes a workflow on an external system (AFIP electronic invoicing). In the context of Argentine tax authority invoicing, re-triggering a workflow could resubmit tax documents, invoices, or fiscal transactions. It creates new executions rather than simply reading data, and given the financial/tax context, misuse could result in duplicate invoice submissions or fiscal errors.

From the tool's definition 'Retry a failed, expired, or rejected workflow execution. Creates a new workflow execution' — triggers a new external workflow/process execution

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

POLICY

How to control retry_transaction

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "retry_transaction": {
      "limits": [
        {
          "counter": "retry_transaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

retry_transaction stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Mcp Afip — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Mcp Afip tools

Financial authorize_transaction Authorize a transaction (reserve funds without capturing) via Braintree GraphQL authorizeP Financial cancel_collection Cancel a scheduled collection request Financial cancel_credit Cancel an authorized-but-uncaptured credit payment. Financial cancel_payment Attempt to cancel a payment that has not yet settled. Iniciador endpoint: POST /payments/{ Financial cancel_payment_intent Cancel a payment intent that has not yet been captured. Fails on already-captured intents; Financial cancel_recurrence Cancel an active recurrence. Future charges will stop; already-charged cycles are untouche Financial cancel_subscription Cancel a subscription by ID Financial revoke_token Revoke an issued access_token or refresh_token at POST /v1/token/revoke. Use to terminate

All 1300 Mcp Afip tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Mcp Afip → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about retry_transaction

What does the retry_transaction tool do? +

Retry a failed, expired, or rejected workflow execution. Creates a new workflow execution on the same account, optionally re-using the original workflow definition and customer references. It is categorised as a Execute tool in the Mcp Afip MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retry_transaction? +

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

retry_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retry_transaction? +

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

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

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

CHECK YOUR STACK →

Free to start. No card required.

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