AI agents call get_modified_document 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 'get_' prefix strongly indicates a query/retrieval operation. Even though the description is empty, contextual analysis of the sibling tools (which include write operations like add_*, apply_modifications_to_document) suggests this tool retrieves the current document state rather than modifying it. No evidence suggests data deletion, code execution, financial transactions, or irreversible changes.
From the tool's definition Tool name is 'get_modified_document' which suggests retrieval of a document state. Description is empty, limiting direct evidence, but the name pattern 'get_*' is typically associated with read operations that retrieve data without side effects.
Documented attack patterns abuse exactly the kind of access get_modified_document 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_modified_document:
{
"version": "1",
"default": "deny",
"tools": {
"get_modified_document": {}
}
}get_modified_document 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_modified_document. 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_modified_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 Docx_MCP_cj. Nothing to install.
get_modified_document 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_modified_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 get_modified_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.
get_modified_document 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.