Lists all Stitch projects accessible to the authenticated user.
AI agents call list_projects to retrieve information from Stitch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays data (project listings) without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval operation, making it a Read category tool. Severity is low because listing projects poses minimal risk even if misused by an AI agent—it only exposes project metadata that the authenticated user already has access to.
From the tool's definition Tool name 'list_projects' and description 'Lists all Stitch projects accessible to the authenticated user' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Lists all Stitch projects accessible to the authenticated user. It is categorised as a Read tool in the Stitch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stitch MCP Server 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 Stitch MCP Server. 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 Stitch MCP Server MCP server (oogleyskr/stitch-mcp-server). 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 →