AI agents call get_intelligent_planning_guide to retrieve information from Docx_MCP_cj without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty, the tool name strongly implies a query/retrieval operation that returns information without modifying any documents. In context with sibling tools that clearly perform writes (add_*, apply_modifications_*), this tool appears designed for information retrieval. Confidence is moderate due to the absence of descriptive documentation.
From the tool's definition The tool name 'get_intelligent_planning_guide' suggests retrieval of a guide or reference material. The empty description prevents confirmation of side effects, but the 'get_' prefix and lack of any modification verbs indicate a read operation.
Documented attack patterns abuse exactly the kind of access get_intelligent_planning_guide gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for get_intelligent_planning_guide:
{
"version": "1",
"default": "deny",
"tools": {
"get_intelligent_planning_guide": {}
}
}get_intelligent_planning_guide 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.
get_intelligent_planning_guide. It is categorised as a Read tool in the Docx_MCP_cj MCP Server, which means it retrieves data without modifying state.
Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for get_intelligent_planning_guide: 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 Docx_MCP_cj. Nothing to install.
get_intelligent_planning_guide 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 get_intelligent_planning_guide 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 get_intelligent_planning_guide. 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.
get_intelligent_planning_guide is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.