AI agents use add_heading 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.
The tool adds a heading to a Word document, which is a write operation that modifies the document structure but remains reversible. It does not delete, execute code, or cause financial impact. Severity is medium because inappropriate heading additions could clutter or misrepresent document structure, but the effects are easily correctable.
From the tool's definition Tool name 'add_heading' and description '添加标题' (Chinese for 'add heading') indicate insertion of content into a document. This is a document modification operation that creates new content reversibly.
Documented attack patterns abuse exactly the kind of access add_heading 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 add_heading:
{
"version": "1",
"default": "deny",
"tools": {
"add_heading": {
"limits": [
{
"counter": "add_heading_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_heading 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.
添加标题. 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 add_heading: 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.
add_heading 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 add_heading 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 add_heading. 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.
add_heading 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.