AI agents use resolve_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 or modifies data reversibly by updating the status of a comment thread. The action can be undone (comments can be re-opened), so it is not Destructive. It does not delete data, execute arbitrary code, or incur financial obligations. The impact is contained to comment thread state within a single project, justifying medium severity rather than high.
From the tool's definition 'Marks a thread as resolved' — modifies the state of a comment thread in the Overleaf project, a reversible operation that changes metadata.
Attacks that exploit this kind of access
Marks a thread as resolved. Use after addressing the comment (e.g. by editing the doc and replying). 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 resolve_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.
resolve_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 resolve_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 resolve_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.
resolve_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 →