List all design systems for a project, or global design systems if no projectId.
AI agents call list_design_systems to retrieve information from Stitch-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of design systems without modifying, creating, deleting, or executing any operations. It is purely informational and has no capability to cause harm or create unintended side effects. The blast radius is minimal—an AI agent cannot misuse this tool to cause harm beyond potentially accessing information it shouldn't, which is a read-level risk.
From the tool's definition Tool name 'list_design_systems' and description 'List all design systems for a project, or global design systems if no projectId' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all design systems for a project, or global design systems if no projectId. It is categorised as a Read tool in the Stitch-MCP MCP Server, which means it retrieves data without modifying state.
Register the Stitch- MCP server in PolicyLayer and add a rule for list_design_systems: 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. Nothing to install.
list_design_systems 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_design_systems 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_design_systems. 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_design_systems is provided by the Stitch- MCP server (samueljayasingh/stitchmcp). 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 →