AI agents use basic_table_fill 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.
The tool fills Word document tables, which is a reversible modification of document content. This is a Write operation rather than Read (it modifies, not just queries) or Execute (it doesn't run arbitrary code). Severity is medium because an AI agent misusing this could corrupt document structure or fill tables with incorrect data, but the operation is reversible via undo.
From the tool's definition Tool name 'basic_table_fill' and server description 'fill any Word document tables' indicates the tool modifies document content. Sibling tools like 'add_table_row', 'add_paragraph', 'add_image' are all Write operations.
Documented attack patterns abuse exactly the kind of access basic_table_fill 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 basic_table_fill:
{
"version": "1",
"default": "deny",
"tools": {
"basic_table_fill": {
"limits": [
{
"counter": "basic_table_fill_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}basic_table_fill 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.
basic_table_fill. 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 basic_table_fill: 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.
basic_table_fill 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 basic_table_fill 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 basic_table_fill. 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.
basic_table_fill 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.