Low Risk

retrieve_beneficiary

Retrieve a beneficiary by id. Returns bank details, entity_type, and allowed payment_methods.

How to control retrieve_beneficiary ↓

What retrieve_beneficiary does on Mcp Afip

AI agents call retrieve_beneficiary 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 retrieve_beneficiary needs a policy

The tool retrieves and queries beneficiary information without creating, modifying, or deleting data. While it exposes sensitive banking details (which warrants 'low' severity rather than minimal), the operation itself is read-only with no side effects or ability to transfer funds or alter records. The exposure of bank details is a data sensitivity concern but does not change the functional category from Read.

From the tool's definition Tool description states 'Retrieve a beneficiary by id' and 'Returns bank details, entity_type, and allowed payment_methods' — purely retrieval operation with no modification, deletion, or financial transaction.

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

How to control retrieve_beneficiary

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

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

retrieve_beneficiary 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 retrieve_beneficiary

What does the retrieve_beneficiary tool do? +

Retrieve a beneficiary by id. Returns bank details, entity_type, and allowed payment_methods. 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 retrieve_beneficiary? +

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

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

Can I rate-limit retrieve_beneficiary? +

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

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

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