AI agents use add_table_row 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 creates or modifies document content (adding a table row) in a reversible manner. It does not execute code, delete data, move money, or trigger external operations. The effect is confined to adding structured data to a document, which is a Write-category operation. Severity is medium because misuse could add many rows or corrupt document structure, but the operation is reversible.
From the tool's definition Tool name 'add_table_row' indicates adding/inserting a row into a document table. The server description mentions '42 MCP tools' for analyzing and filling Word document tables, and sibling tools like 'add_table', 'add_paragraph', 'add_image' confirm this is a…
Documented attack patterns abuse exactly the kind of access add_table_row 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 add_table_row:
{
"version": "1",
"default": "deny",
"tools": {
"add_table_row": {
"limits": [
{
"counter": "add_table_row_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_table_row 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.
add_table_row. 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 add_table_row: 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.
add_table_row 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 add_table_row 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 add_table_row. 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.
add_table_row 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.