Search transactions via the GraphQL search.transactions query. Filter by status / customerId / orderId / createdAt range. Returns a page of transaction nodes with id, status, amount, orderId, createdAt.
AI agents call search_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.
This is a query operation that retrieves financial transaction data without side effects. While the data is sensitive (transaction history), the tool only performs filtering and retrieval. The blast radius of misuse is limited to unauthorized information disclosure rather than financial harm, data destruction, or execution of arbitrary operations.
From the tool's definition Tool description states it 'Search transactions' and 'Returns a page of transaction nodes' with read-only fields (id, status, amount, orderId, createdAt). No mutation, creation, deletion, or modification of data is described.
Documented attack patterns abuse exactly the kind of access search_transactions gives an agent:
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 search_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"search_transactions": {}
}
}search_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search transactions via the GraphQL search.transactions query. Filter by status / customerId / orderId / createdAt range. Returns a page of transaction nodes with id, status, amount, orderId, createdAt. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.
Register the Mcp Afip MCP server in PolicyLayer and add a rule for search_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.
search_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_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.
Set action: deny in the PolicyLayer policy for search_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.
search_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.
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.