Set borders on all six sides of a table (top, bottom, left, right, insideH, insideV).
AI agents use set_table_borders 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 structure (table borders) reversibly—users can change borders again or remove them. It does not execute code, delete data irreversibly, or access external systems. The modification is cosmetic/structural and poses minimal risk even if misused by an agent, as border changes can be easily undone. Classified as Write rather than Read because it modifies the document state.
From the tool's definition Tool modifies table borders (top, bottom, left, right, insideH, insideV) in a Word document. The description explicitly states the tool 'Set borders' on table elements, which is a reversible modification of document formatting.
Documented attack patterns abuse exactly the kind of access set_table_borders 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_table_borders:
{
"version": "1",
"default": "deny",
"tools": {
"set_table_borders": {
"limits": [
{
"counter": "set_table_borders_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_table_borders 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 borders on all six sides of a table (top, bottom, left, right, insideH, insideV). 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_table_borders: 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_table_borders 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_table_borders 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_table_borders. 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_table_borders 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.