AI agents call get_tool_detailed_guidance 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.
The tool appears to fetch guidance or documentation about other tools. This is a read-only information retrieval operation. With no description provided, confidence is moderate rather than high, but the naming pattern and function within a documentation context strongly suggest it performs queries without modification, creation, or execution of external operations.
From the tool's definition Tool name 'get_tool_detailed_guidance' indicates a retrieval operation. The empty description prevents full certainty, but the verb 'get' and context of a documentation/guidance system suggest data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_tool_detailed_guidance 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_tool_detailed_guidance:
{
"version": "1",
"default": "deny",
"tools": {
"get_tool_detailed_guidance": {}
}
}get_tool_detailed_guidance 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_tool_detailed_guidance. 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_tool_detailed_guidance: 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_tool_detailed_guidance 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_tool_detailed_guidance 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_tool_detailed_guidance. 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_tool_detailed_guidance 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.