set_paragraph_border
AI agents use set_paragraph_border 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.
This tool creates or modifies document formatting (paragraph borders) without deleting data or executing arbitrary code. The modification is reversible—borders can be removed or changed. While the description is empty, the server's explicit editing capability and the nature of border-setting operations (a standard document property modification) clearly places this in the Write category.
From the tool's definition Tool name 'set_paragraph_border' indicates modification of document formatting properties. Server description states the MCP enables 'editing...Microsoft Word documents' and 'precise OOXML-level document manipulation'.
Documented attack patterns abuse exactly the kind of access set_paragraph_border gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for set_paragraph_border:
{
"version": "1",
"default": "deny",
"tools": {
"set_paragraph_border": {
"limits": [
{
"counter": "set_paragraph_border_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_paragraph_border 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.
set_paragraph_border. 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_paragraph_border: 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_paragraph_border 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_paragraph_border 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_paragraph_border. 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_paragraph_border 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.
Start from 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.