Checks if there is an existing Stitch project associated with the current workspace/folder. Returns project info if found, or null if no project is set. Use this at the start of a session to check for existing projects.
AI agents call get_workspace_project 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 is a simple query operation that checks for and retrieves existing project metadata. It has no side effects, cannot modify or delete data, and poses minimal risk if misused by an AI agent. Classified as Read with low severity.
From the tool's definition Tool retrieves and returns project information ('Returns project info if found, or null if no project is set'); no data modification, deletion, or external execution occurs—purely informational lookup.
Attacks that exploit this kind of access
Checks if there is an existing Stitch project associated with the current workspace/folder. Returns project info if found, or null if no project is set. Use this at the start of a session to check for existing 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 get_workspace_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 Stitch MCP Server. Nothing to install.
get_workspace_project 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 get_workspace_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.
Set action: deny in the PolicyLayer policy for get_workspace_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.
get_workspace_project 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 →