IDCloud: tamper / forgery detection on a document image. Returns an authenticity score (0-1), a categorical verdict (AUTHENTIC | SUSPICIOUS | FRAUDULENT), and a list of detected anomalies (e.g. font mismatch, copy-paste edits, printed-on-screen capture).
AI agents call verify_document_authenticity 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.
verify_document_authenticity is a read-only operation that analyzes and retrieves information about document authenticity. It queries document properties and returns detection results without altering data, executing code, triggering external operations with unpredictable effects, deleting information, or moving money.
From the tool's definition Tool performs document verification and analysis returning 'an authenticity score (0-1), a categorical verdict (AUTHENTIC | SUSPICIOUS | FRAUDULENT), and a list of detected anomalies'. It does not modify, execute, delete, or transfer funds.
Documented attack patterns abuse exactly the kind of access verify_document_authenticity 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 verify_document_authenticity:
{
"version": "1",
"default": "deny",
"tools": {
"verify_document_authenticity": {}
}
}verify_document_authenticity 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.
IDCloud: tamper / forgery detection on a document image. Returns an authenticity score (0-1), a categorical verdict (AUTHENTIC | SUSPICIOUS | FRAUDULENT), and a list of detected anomalies (e.g. font mismatch, copy-paste edits, printed-on-screen capture). 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 verify_document_authenticity: 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.
verify_document_authenticity 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 verify_document_authenticity 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 verify_document_authenticity. 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.
verify_document_authenticity 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.