Retrieve a charge by the merchant-side orderNumber (order_id passed to create_charge). Use when you have the merchant reference but not the Izipay charge id.
AI agents call get_charge_by_order 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 tool retrieves existing charge information by a merchant order reference. It has no side effects—it does not create, modify, delete, or execute actions. The blast radius of misuse is minimal: an unauthorized retrieval of charge metadata poses low risk compared to financial transactions, destructive operations, or code execution. Classified as Read with low severity.
From the tool's definition Tool name 'get_charge_by_order' and description 'Retrieve a charge' indicate a query operation that fetches data without modification.
Documented attack patterns abuse exactly the kind of access get_charge_by_order 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 get_charge_by_order:
{
"version": "1",
"default": "deny",
"tools": {
"get_charge_by_order": {}
}
}get_charge_by_order 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.
Retrieve a charge by the merchant-side orderNumber (order_id passed to create_charge). Use when you have the merchant reference but not the Izipay charge id. 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 get_charge_by_order: 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.
get_charge_by_order 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 get_charge_by_order 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 get_charge_by_order. 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.
get_charge_by_order 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.