Low Risk

extract_document

IDCloud: OCR + structured field extraction from a Brazilian ID document image. Returns typed fields (name, document number, issuer, birthdate, parents, etc.) plus extraction confidence.

How to control extract_document ↓

What extract_document does on Mcp Afip

AI agents call extract_document 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.

Low Risk

Why extract_document needs a policy

This is fundamentally a read operation—it extracts and returns data from a document without altering or destroying it. However, severity is elevated to 'medium' because the tool processes sensitive personally identifiable information (PII) including name, document number, birthdate, and parental information from ID documents.

From the tool's definition Tool performs OCR and 'structured field extraction from a Brazilian ID document image' returning 'typed fields' with 'extraction confidence'. No modifications, deletions, or code execution described.

Documented attack patterns abuse exactly the kind of access extract_document gives an agent:

How to control extract_document

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 extract_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_document": {}
  }
}

extract_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Afip — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about extract_document

What does the extract_document tool do? +

IDCloud: OCR + structured field extraction from a Brazilian ID document image. Returns typed fields (name, document number, issuer, birthdate, parents, etc.) plus extraction confidence. It is categorised as a Read tool in the Mcp Afip MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on extract_document? +

Register the Mcp Afip MCP server in PolicyLayer and add a rule for extract_document: 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.

What risk level is extract_document? +

extract_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit extract_document? +

Yes. Add a rate_limit block to the extract_document 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.

How do I block extract_document completely? +

Set action: deny in the PolicyLayer policy for extract_document. 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.

What MCP server provides extract_document? +

extract_document 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.

Enforce policy on every Mcp Afip tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.