AI agents use modify_table_structure to create or update resources in Docx_MCP_cj — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx_MCP_cj environment.
This tool modifies document structure reversibly (tables can be re-edited). It is not Destructive because table modifications are generally undoable via document version history or manual editing. It is not Execute because it does not run arbitrary code or trigger external operations—it operates within the confined domain of Word document table structure.
From the tool's definition Tool named 'modify_table_structure' on a document manipulation server (Docx_MCP_cj) that 'enables AI agents to intelligently analyze and fill any Word document tables.' The sibling tools include add_table, add_table_row, add_table_column, and…
Documented attack patterns abuse exactly the kind of access modify_table_structure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for modify_table_structure:
{
"version": "1",
"default": "deny",
"tools": {
"modify_table_structure": {
"limits": [
{
"counter": "modify_table_structure_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}modify_table_structure 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.
modify_table_structure. It is categorised as a Write tool in the Docx_MCP_cj MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for modify_table_structure: 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_MCP_cj. Nothing to install.
modify_table_structure 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 modify_table_structure 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 modify_table_structure. 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.
modify_table_structure is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.