Retrieve a previously-run check by ID (person, company, or document). Useful for replay + auditing without re-querying datasources. GET /v1/checks/{check_id}.
AI agents call get_check_result 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 queries existing check records from the AFIP system. It has no capacity to modify, delete, or execute operations. The retrieval of tax authority check data carries minimal risk in an agentic context, as the agent cannot alter records or trigger financial transactions through a read-only operation. Confidence is high because the description is explicit about retrieval semantics.
From the tool's definition 'Retrieve a previously-run check by ID' — the tool retrieves historical check results without modification. The HTTP method is explicitly GET. No side effects or data changes occur.
Documented attack patterns abuse exactly the kind of access get_check_result 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_check_result:
{
"version": "1",
"default": "deny",
"tools": {
"get_check_result": {}
}
}get_check_result 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 previously-run check by ID (person, company, or document). Useful for replay + auditing without re-querying datasources. GET /v1/checks/{check_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_check_result: 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_check_result 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_check_result 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_check_result. 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_check_result 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.