AI agents invoke process_document to trigger actions in OCR-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
With no description available, classification is based on the tool name and server context. 'Process' implies an execution action (running OCR pipelines, transforming documents). The server involves multiple OCR backends and workflow execution, suggesting this tool triggers document processing operations rather than simply reading or writing data. Confidence is lowered due to the empty description.
From the tool's definition Tool name is 'process_document'; description is empty or uninformative. Server context mentions document processing with OCR backends.
Documented attack patterns abuse exactly the kind of access process_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OCR-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for process_document:
{
"version": "1",
"default": "deny",
"tools": {
"process_document": {
"limits": [
{
"counter": "process_document_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}process_document stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
process_document. It is categorised as a Execute tool in the OCR-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OCR- MCP server in PolicyLayer and add a rule for process_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 OCR-MCP. Nothing to install.
process_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the process_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.
Set action: deny in the PolicyLayer policy for process_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.
process_document is provided by the OCR- MCP server (sandraschi/ocr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OCR-MCP, 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.
8 OCR-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.