Write a DOCX table of all redactions made this session.
AI agents use generate_redaction_log to create or update resources in Docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
This tool generates and inserts a new table into a Word document—a reversible modification operation. It does not delete, destroy, or execute arbitrary code; it simply documents redactions by creating a structured log table. Write is the appropriate category, and severity is low because the operation is limited in scope (creating a log table), non-destructive, and auxiliary to document management.
From the tool's definition Tool description states 'Write a DOCX table', explicitly invoking write semantics. The tool creates a new table within the document to log redactions performed in the current session.
Documented attack patterns abuse exactly the kind of access generate_redaction_log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_redaction_log:
{
"version": "1",
"default": "deny",
"tools": {
"generate_redaction_log": {
"limits": [
{
"counter": "generate_redaction_log_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate_redaction_log 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.
Write a DOCX table of all redactions made this session. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx MCP server in PolicyLayer and add a rule for generate_redaction_log: 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. Nothing to install.
generate_redaction_log 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 generate_redaction_log 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 generate_redaction_log. 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.
generate_redaction_log is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 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.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.