AI agents use set_page_margins 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 modifies document properties (page margins) in a reversible manner. This is Write-category because it changes document state without deleting data or executing arbitrary code. Severity is medium because incorrect margin settings could affect document layout and readability, but the change is easily undone. The tool operates within the document manipulation context of this Word document server.
From the tool's definition Tool name 'set_page_margins' with description '设置页面边距' (set page margins) modifies document formatting. This is reversible document modification, similar to sibling tools like 'add_paragraph' and 'add_table' which are Write operations.
Documented attack patterns abuse exactly the kind of access set_page_margins 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 set_page_margins:
{
"version": "1",
"default": "deny",
"tools": {
"set_page_margins": {
"limits": [
{
"counter": "set_page_margins_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_page_margins 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 set_page_margins: 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.
set_page_margins 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 set_page_margins 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 set_page_margins. 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.
set_page_margins 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.