reject_changes · Overleaf MCP: Risk & Policy

WHAT IT DOES

What reject_changes does on Overleaf

AI agents use reject_changes 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.

WHY IT NEEDS A POLICY

Why reject_changes needs a policy

The tool modifies tracked changes in a LaTeX document by accepting or rejecting suggestions. This is a write operation because it alters document content (removing insertions, clearing strikethrough) in a reversible manner. It does not permanently delete data—rejected changes can be re-applied or the document version can be reverted.

From the tool's definition "Rejects the specified tracked-change suggestions. For tracked inserts the inserted text is removed; for tracked deletes the strikethrough is cleared and the text stays." This modifies document state by removing inserted text or clearing deletion markers,…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_changes Rate-limited

reject_changes 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reject_changes": {
      "limits": [
        {
          "counter": "reject_changes_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Overleaf, so you can run agents against it safely.

FAQ

Questions about reject_changes

What does the reject_changes tool do? +

Rejects the specified tracked-change suggestions. For tracked inserts the inserted text is removed; for tracked deletes the strikethrough is cleared and the text stays. Implemented as an OT update with. 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.

How do I enforce a policy on reject_changes? +

Register the Overleaf MCP server in PolicyLayer and add a rule for reject_changes: 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.

What risk level is reject_changes? +

reject_changes is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reject_changes? +

Yes. Add a rate_limit block to the reject_changes 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.

How do I block reject_changes completely? +

Set action: deny in the PolicyLayer policy for reject_changes. 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.

What MCP server provides reject_changes? +

reject_changes 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.