AI agents use add_text_to_document to create or update resources in Office Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Office Editor environment.
This tool creates or modifies document content reversibly—text can be edited or removed. It does not execute arbitrary code, delete data irreversibly, or move money. The lack of a detailed description slightly lowers confidence, but the name and server context make the Write category clear.
From the tool's definition Tool name 'add_text_to_document' indicates it creates or modifies document content. The server description confirms this is an 'MCP server for creating and editing Word, Excel, and PowerPoint documents.' The sibling tools (add_slide, add_text_box,…
Documented attack patterns abuse exactly the kind of access add_text_to_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Office Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for add_text_to_document:
{
"version": "1",
"default": "deny",
"tools": {
"add_text_to_document": {
"limits": [
{
"counter": "add_text_to_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_text_to_document 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.
add_text_to_document. It is categorised as a Write tool in the Office Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Office Editor MCP server in PolicyLayer and add a rule for add_text_to_document: 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 Editor. Nothing to install.
add_text_to_document 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_text_to_document 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_text_to_document. 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_text_to_document is provided by the Office Editor MCP server (thewdy/office-editor-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 88 Office Editor tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
88 Office Editor tools catalogued and risk-classified — across an index of 42,500+ MCP servers.