Low Risk

get_b2p_transfer

Get the status of a B2P transfer by referenceId. Typical statuses: created, processing, completed, failed.

How to control get_b2p_transfer ↓

What get_b2p_transfer does on Mcp Afip

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

This tool queries the status of an existing B2P (business-to-person) transfer without modifying, deleting, or executing any financial transactions. It is a read-only operation that retrieves information about a transfer's state. While it operates within a financial domain (AFIP tax authority invoicing), the tool itself performs no financial operations—it merely reads status data.

From the tool's definition Tool name is 'get_b2p_transfer' and description states 'Get the status of a B2P transfer by referenceId.' The verb 'Get' and the phrase 'get the status' indicate a retrieval operation with no side effects.

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

How to control get_b2p_transfer

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

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

get_b2p_transfer 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_b2p_transfer

What does the get_b2p_transfer tool do? +

Get the status of a B2P transfer by referenceId. Typical statuses: created, processing, completed, failed. 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_b2p_transfer? +

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

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

Can I rate-limit get_b2p_transfer? +

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

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

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