AI agents use reply_comment to create or update resources in Overleaf — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overleaf environment.
This tool creates new data (comment replies) reversibly within an existing thread. It is not destructive since replies can be deleted or edited later. It does not execute code or trigger financial transactions. While it modifies the document's collaborative state, the change is non-destructive and typical of collaborative Write operations.
From the tool's definition Tool description states 'Adds a new message to an existing comment thread', which indicates creating new comment data within Overleaf's collaboration system.
Attacks that exploit this kind of access
Adds a new message to an existing comment thread. Threads come from. It is categorised as a Write tool in the Overleaf MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Overleaf MCP server in PolicyLayer and add a rule for reply_comment: 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 Overleaf. Nothing to install.
reply_comment 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 reply_comment 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 reply_comment. 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.
reply_comment is provided by the Overleaf MCP server (netique/overleaf-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 →