Document validation — OCR + authenticity check on RG / CNH / passport / proof of residence. Returns structured fields + authenticity_score. POST /v1/checks/document.
AI agents call document_check 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 and validates document data without creating, modifying, deleting, or executing arbitrary operations. It extracts information (OCR) and computes a verification metric (authenticity score), classifying it as Read.
From the tool's definition Tool performs document validation via OCR and authenticity checking, returning structured fields and an authenticity score. No modification, deletion, or financial transaction occurs.
Documented attack patterns abuse exactly the kind of access document_check 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 document_check:
{
"version": "1",
"default": "deny",
"tools": {
"document_check": {}
}
} document_check 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.
Document validation — OCR + authenticity check on RG / CNH / passport / proof of residence. Returns structured fields + authenticity_score. POST /v1/checks/document. 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 document_check: 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.
document_check 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 document_check 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 document_check. 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.
document_check 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.