generate_docx_report
AI agents use generate_docx_report to create or update resources in Q1-Reviewer-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Q1-Reviewer-MCP environment.
The tool creates and writes a new document file (.docx format) that is a decision letter for academic manuscripts. This is a Write operation (creates data reversibly) rather than Read (no document generation), Execute (not running arbitrary code), Destructive (file creation is reversible), or Financial (no money involved).
From the tool's definition Tool name 'generate_docx_report' indicates it creates a formatted .docx file; server description states it 'generate[s] a formatted .docx decision letter'.
Attacks that exploit this kind of access
generate_docx_report. It is categorised as a Write tool in the Q1-Reviewer-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Q1-Reviewer- MCP server in PolicyLayer and add a rule for generate_docx_report: 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 Q1-Reviewer-MCP. Nothing to install.
generate_docx_report 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_docx_report 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_docx_report. 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_docx_report is provided by the Q1-Reviewer- MCP server (muslus/q1-reviewer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →