Wait for a PDF parse task until success and return merged text. Prefer passing uid (no re-submit). If only pdf_path is provided, it will (a) reuse an in-process cached uid if available, otherwise (b) submit a new task then wait.
AI agents invoke doc2x_parse_pdf_wait_text to trigger actions in Doc2x MCP Server. 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.
This tool triggers asynchronous external operations (submitting and waiting for a PDF parse task via the Doc2x API). It executes an external processing pipeline rather than simply reading local data. It may also submit a new task if no cached uid is available, making it an active operation with external side effects.
From the tool's definition Wait for a PDF parse task until success and return merged text... submit a new task then wait
Attacks that exploit this kind of access
Wait for a PDF parse task until success and return merged text. Prefer passing uid (no re-submit). If only pdf_path is provided, it will (a) reuse an in-process cached uid if available, otherwise (b) submit a new task then wait. It is categorised as a Execute tool in the Doc2x MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Doc2x MCP Server MCP server in PolicyLayer and add a rule for doc2x_parse_pdf_wait_text: 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 Doc2x MCP Server. Nothing to install.
doc2x_parse_pdf_wait_text 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 doc2x_parse_pdf_wait_text 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 doc2x_parse_pdf_wait_text. 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.
doc2x_parse_pdf_wait_text is provided by the Doc2x MCP Server MCP server (noedgeai/doc2x-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 →