clone_project · Overleaf MCP Server MCP: Risk & Policy

WHAT IT DOES

What clone_project does on Overleaf MCP Server

AI agents use clone_project to create or update resources in Overleaf MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Overleaf MCP Server environment.

WHY IT NEEDS A POLICY

Why clone_project needs a policy

Cloning a project is a write operation that creates new files and directories locally. It is not destructive (no deletion), not financial, and not execute (though it may trigger git operations, the tool itself is primarily about creating local state). Severity is medium because unauthorized cloning could expose sensitive LaTeX project contents, but the operation is reversible (cloned files can be deleted).

From the tool's definition Tool description states 'Clone an Overleaf project to a local directory' – this creates a local copy of project data, which is a write operation that modifies the local filesystem by adding new files and directories.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clone_project Rate-limited

clone_project 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": {
    "clone_project": {
      "limits": [
        {
          "counter": "clone_project_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about clone_project

What does the clone_project tool do? +

Clone an Overleaf project to a local directory. It is categorised as a Write tool in the Overleaf MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on clone_project? +

Register the Overleaf MCP Server MCP server in PolicyLayer and add a rule for clone_project: 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 MCP Server. Nothing to install.

What risk level is clone_project? +

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

Can I rate-limit clone_project? +

Yes. Add a rate_limit block to the clone_project 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 clone_project completely? +

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

clone_project is provided by the Overleaf MCP Server MCP server (juho127/overleafmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.