AI agents call list_projects to retrieve information from Overleaf without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves a list of existing projects from the user's Overleaf account. It has no side effects—it does not create, modify, delete, or execute any operations. The only concern is potential information disclosure if credentials are compromised, but the tool itself is a standard data retrieval function with minimal blast radius.
From the tool's definition Tool name 'list_projects' and description 'Lists projects on the configured Overleaf account' indicate a query operation that retrieves and returns data without modification, creation, deletion, or execution of external operations.
Attacks that exploit this kind of access
Lists projects on the configured Overleaf account, sorted by most recently updated. It is categorised as a Read tool in the Overleaf MCP Server, which means it retrieves data without modifying state.
Register the Overleaf MCP server in PolicyLayer and add a rule for list_projects: 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.
list_projects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_projects 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 list_projects. 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.
list_projects 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 →