Split table into two tables at specified row Parameters: - table_index: Table index - row_index: Split table after this row
AI agents use split_table 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 creates a structural modification to a docx document by splitting a table, which is a write operation. While it reorganizes content, it does not permanently delete data (making it Write rather than Destructive). The modification is reversible by merging tables back.
From the tool's definition Tool description states 'Split table into two tables' which modifies document structure by reorganizing table data.
Documented attack patterns abuse exactly the kind of access split_table 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 split_table:
{
"version": "1",
"default": "deny",
"tools": {
"split_table": {
"limits": [
{
"counter": "split_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Split table into two tables at specified row Parameters: - table_index: Table index - row_index: Split table after this row. 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 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 Doc/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 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.