AI agents use fill_with_coordinates 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 modifies document content (filling table cells with data) reversibly. While the description is empty, the server's stated purpose and sibling tools (add_table, add_paragraph, add_text_with_formatting) confirm this is a Write operation.
From the tool's definition Tool name 'fill_with_coordinates' combined with server description stating it 'fill[s] any Word document tables using precise coordinate-based filling.' The description is empty, limiting direct evidence, but the server context indicates document modification…
Documented attack patterns abuse exactly the kind of access fill_with_coordinates 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 fill_with_coordinates:
{
"version": "1",
"default": "deny",
"tools": {
"fill_with_coordinates": {
"limits": [
{
"counter": "fill_with_coordinates_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}fill_with_coordinates 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.
fill_with_coordinates. 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 fill_with_coordinates: 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.
fill_with_coordinates 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 fill_with_coordinates 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 fill_with_coordinates. 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.
fill_with_coordinates 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.