list_projects
List all available Stitch projects
This record as markdown: /tools/0x-professor-stitch-mcp-server/list-projects.md
What list_projects does on Stitch MCP Server
AI agents call list_projects to retrieve information from Stitch MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_projects is rated Low
This tool performs a read-only operation that retrieves metadata about projects. It has no side effects and does not create, modify, delete, or execute anything. The blast radius if misused is minimal—an AI agent listing projects cannot cause data loss or unintended actions beyond visibility of project names/metadata.
From the tool's definition Tool is named 'list_projects' and described as 'List all available Stitch projects', which retrieves or queries data without modifying or executing code.
Attacks that exploit this kind of access
The rule that runs list_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stitch MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_projects, this is the rule to start with:
list_projects is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stitch MCP Server, apply this rule, and every list_projects call is checked against it from then on.
Questions about list_projects
List all available Stitch projects. 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 (0x-professor/stitch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stitch MCP Server, and thousands of servers like it.
This server
Across the catalogue