Find specified title in document and replace content under that title, keeping original position, format, and style Parameters: - section_title: Title text to find - new_content: New content list, each element is a paragraph - preserve_title: Whether to keep original title, default is True
AI agents use replace_section to create or update resources in Doc/docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc/docx environment.
This tool modifies document content by finding a section and replacing its contents while preserving structure, position, format, and style. This is a reversible Write operation — the original content is overwritten but not irreversibly deleted and can be recovered via undo or version history. It does not permit data deletion (category: Destructive) or code execution (category: Execute).
From the tool's definition Tool description states 'replace content under that title' and 'Find specified title in document and replace content'. The parameters include 'new_content' indicating modification of existing document sections.
Documented attack patterns abuse exactly the kind of access replace_section gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc/docx, and nothing reaches the server without passing your rules. This is the rule we recommend for replace_section:
{
"version": "1",
"default": "deny",
"tools": {
"replace_section": {
"limits": [
{
"counter": "replace_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}replace_section 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.
Find specified title in document and replace content under that title, keeping original position, format, and style Parameters: - section_title: Title text to find - new_content: New content list, each element is a paragraph - preserve_title: Whether to keep original title, default is True. It is categorised as a Write tool in the Doc/docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc/docx MCP server in PolicyLayer and add a rule for replace_section: 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 Doc/docx. Nothing to install.
replace_section 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 replace_section 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 replace_section. 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.
replace_section is provided by the Doc/docx MCP server (meterlong/mcp-doc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Doc/docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
23 Doc/docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.