Low Risk

get_recurrent

Get recurrent payment details

How to control get_recurrent ↓

What get_recurrent does on Mcp Afip

AI agents call get_recurrent to retrieve information from Mcp Afip without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_recurrent needs a policy

This tool retrieves information about recurrent payment details without modifying, executing, or deleting any data. It is a read-only query operation on payment metadata in the AFIP Argentine tax authority system. While it accesses financial information, it does not move money, commit financial obligations, or execute transactions—it only fetches existing data.

From the tool's definition Tool name 'get_recurrent' and description 'Get recurrent payment details' indicate a retrieval operation with the verb 'Get' and 'details', typical of read-only operations.

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

How to control get_recurrent

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_recurrent": {}
  }
}

get_recurrent is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_recurrent

What does the get_recurrent tool do? +

Get recurrent payment details. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_recurrent? +

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

get_recurrent is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_recurrent? +

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

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

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