Low Risk

get_receivables_transactions

Get receivables transactions for a link (payment rails / acquirer data)

How to control get_receivables_transactions ↓

What get_receivables_transactions does on Mcp Afip

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

This tool retrieves financial transaction data but does not execute payments, modify records, or delete information. It is a passive query operation on the AFIP electronic invoicing system. While it accesses sensitive financial data, the read-only nature and lack of side effects place it in the Read category with low severity. Confidence is high because the description explicitly uses 'Get' (retrieval) language.

From the tool's definition Tool description states 'Get receivables transactions' — a retrieval operation with no modification or destructive intent. The verb 'get' and context of querying 'payment rails / acquirer data' indicate read-only access to transaction history.

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

How to control get_receivables_transactions

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

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

get_receivables_transactions 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_receivables_transactions

What does the get_receivables_transactions tool do? +

Get receivables transactions for a link (payment rails / acquirer data). 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_receivables_transactions? +

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

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

Can I rate-limit get_receivables_transactions? +

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

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

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