🎯 MANDATORY FIRST STEP - Smart Document Conversion Planner - ⚠️ CRITICAL: This tool MUST be executed BEFORE any document conversion operation! When users request any format conversion (e.g.,
AI agents call plan_conversion to retrieve information from Doc Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to be a planning/analysis step that determines how a conversion should be done before any actual conversion is executed. Planning tools typically read inputs and produce a plan or recommendation without side effects. However, the description is truncated ('e.g.,') so full behavior is uncertain, slightly lowering confidence. No evidence of data modification, execution, or destruction.
From the tool's definition 'Smart Document Conversion Planner' and 'MUST be executed BEFORE any document conversion operation' — it plans/analyzes a conversion task rather than performing one
Documented attack patterns abuse exactly the kind of access plan_conversion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for plan_conversion:
{
"version": "1",
"default": "deny",
"tools": {
"plan_conversion": {}
}
}plan_conversion 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.
🎯 MANDATORY FIRST STEP - Smart Document Conversion Planner - ⚠️ CRITICAL: This tool MUST be executed BEFORE any document conversion operation! When users request any format conversion (e.g.,. It is categorised as a Read tool in the Doc Ops MCP Server, which means it retrieves data without modifying state.
Register the Doc Ops MCP server in PolicyLayer and add a rule for plan_conversion: 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 Doc Ops. Nothing to install.
plan_conversion 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 plan_conversion 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 plan_conversion. 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.
plan_conversion is provided by the Doc Ops MCP server (tele-ai/doc-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Doc Ops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Doc Ops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.