add_word_header_footer
AI agents use add_word_header_footer to create or update resources in Office MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office MCP Server environment.
This tool creates or modifies document content (headers/footers in Word) reversibly, which is characteristic of Write operations. While the description is empty, the tool name combined with server context and sibling tool patterns clearly indicates document modification capability.
From the tool's definition Tool name 'add_word_header_footer' indicates it adds/modifies headers and footers in Word documents. Server description states it enables 'creating, editing, and processing Word, Excel, and PowerPoint documents.' The 'add_' prefix and sibling tools…
Attacks that exploit this kind of access
add_word_header_footer. It is categorised as a Write tool in the Office MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office MCP Server MCP server in PolicyLayer and add a rule for add_word_header_footer: 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 Office MCP Server. Nothing to install.
add_word_header_footer 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_word_header_footer 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_word_header_footer. 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_word_header_footer is provided by the Office MCP Server MCP server (walkingzzzy/office-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →