AI agents use prepare_document_for_download to create or update resources in Docx_MCP_cj — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx_MCP_cj environment.
This tool uploads a file to cloud storage (Alibaba Cloud OSS) and returns a download link. It writes/creates data in an external storage system. While it involves an external service, it is a reversible write operation (uploading a file), not destructive, financial, or executing arbitrary code.
From the tool's definition 将修改后的 .docx 文件上传到阿里云OSS，并返回访问链接 (Uploads the modified .docx file to Alibaba Cloud OSS and returns an access link)
Documented attack patterns abuse exactly the kind of access prepare_document_for_download 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 prepare_document_for_download:
{
"version": "1",
"default": "deny",
"tools": {
"prepare_document_for_download": {
"limits": [
{
"counter": "prepare_document_for_download_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}prepare_document_for_download stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
将修改后的 .docx 文件上传到阿里云OSS，并返回访问链接。. It is categorised as a Write tool in the Docx_MCP_cj MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for prepare_document_for_download: 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.
prepare_document_for_download is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the prepare_document_for_download 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 prepare_document_for_download. 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.
prepare_document_for_download 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.