This record as markdown: /tools/securityronin-docx-mcp/split-table.md
What split_table does on Docx
AI agents use split_table 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.
Why split_table is rated Medium
Splitting a table is a reversible modification operation that alters document structure but can be undone. It fits Write category (modifies data reversibly) rather than Destructive (which requires irreversible deletion). Without a description, confidence is moderate but reasonable given the server's editing purpose and sibling tools like add_column_to_table and add_bookmark that are clearly Write operations.
From the tool's definition Tool name 'split_table' on a document editing server (described as enabling 'editing...Microsoft Word documents') indicates a write operation that modifies document structure. No description provided to confirm exact behavior.
Attacks that exploit this kind of access
The rule that runs split_table safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For split_table, this is the rule to start with:
split_table 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every split_table call is checked against it from then on.
Questions about split_table
split_table is a write tool on the Docx MCP server. 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 split_table: 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.
split_table 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 split_table 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 split_table. 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.
split_table 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.
More on Docx, and thousands of servers like it.
This server
Across the catalogue