Create a background OCR ingest job instead of blocking the MCP request.
AI agents invoke ocr_pdf_document to trigger actions in Asset Aware. 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.
The tool initiates a background job (OCR ingest), which is an external operation/execution rather than a simple data read or write. It causes side effects by launching a processing pipeline. It is not purely destructive or financial, but it executes an asynchronous operation with variable effects depending on the input document.
From the tool's definition 'Create a background OCR ingest job' — triggers an external background processing operation whose effects depend on the PDF document provided
Attacks that exploit this kind of access
Create a background OCR ingest job instead of blocking the MCP request. It is categorised as a Execute tool in the Asset Aware MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Asset Aware MCP server in PolicyLayer and add a rule for ocr_pdf_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 Asset Aware. Nothing to install.
ocr_pdf_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 ocr_pdf_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 ocr_pdf_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.
ocr_pdf_document is provided by the Asset Aware MCP server (u9401066/asset-aware-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →