Returns a high-level summary of a Stitch project: screen count, list of screens with names, detected common patterns, design consistency score (based on color/font overlap across screens), and device type distribution.
AI agents call project_summary 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 performs query and retrieval operations only—it fetches and reports aggregate statistics and metadata about an existing project without creating, modifying, deleting, or executing any operations. The read-only nature and absence of side effects place it firmly in the Read category.
From the tool's definition Tool 'returns' project summary data with 'screen count', 'list of screens', 'detected common patterns', 'design consistency score', and 'device type distribution'. Uses passive retrieval language ('Returns'), no modification or deletion of data.
Attacks that exploit this kind of access
Returns a high-level summary of a Stitch project: screen count, list of screens with names, detected common patterns, design consistency score (based on color/font overlap across screens), and device type distribution. 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 project_summary: 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.
project_summary 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 project_summary 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 project_summary. 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.
project_summary 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 →