set_different_first_page
A write tool on the Docx MCP server.
This record as markdown: /tools/securityronin-docx-mcp/set-different-first-page.md
What set_different_first_page does on Docx
AI agents use set_different_first_page to create or update resources in Docx, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
Why set_different_first_page is rated Medium
The tool appears to modify page layout settings (setting a different first page header/footer configuration in Word), which is a reversible write operation on document metadata/formatting. It does not delete data (thus not Destructive), does not execute arbitrary code (thus not Execute), and has no financial impact. The empty description and reliance on naming convention and server context lower confidence to 0.75.
From the tool's definition Tool name 'set_different_first_page' suggests modifying document page formatting properties. Server description states the MCP enables 'editing' and 'OOXML-level document manipulation' of Word documents.
Attacks that exploit this kind of access
The rule that runs set_different_first_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_different_first_page, this is the rule to start with:
set_different_first_page 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every set_different_first_page call is checked against it from then on.
Questions about set_different_first_page
set_different_first_page is a write tool on the Docx MCP server. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx MCP server in PolicyLayer and add a rule for set_different_first_page: 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. Nothing to install.
set_different_first_page 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_different_first_page 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_different_first_page. 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_different_first_page is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
This server
Across the catalogue