list_design_systems

Lists all design systems for a given project.

SERVERMcp SOURCEhttps://stitch.googleapis.com/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-stitch-mcp/list-design-systems.md

WHAT IT DOES

What list_design_systems does on Mcp

AI agents call list_design_systems to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`projectId`	string	—	Optional. The project ID to list design systems for, example: '4044680601076201931', without the `projects/` prefix. If empty, lists all global design systems.

Parameters from the server's own tool schema.

RISK

Why list_design_systems is rated Low

This tool queries and returns data about design systems without modifying, creating, deleting, or executing any operations. It is a straightforward informational read operation, making it low severity with high confidence.

From the tool's definition Tool name is 'list_design_systems' and description states 'Lists all design systems for a given project' — a pure retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_design_systems safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_design_systems, this is the rule to start with:

list_design_systems Allowed

list_design_systems is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_design_systems": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_design_systems call is checked against it from then on.

FAQ

Questions about list_design_systems

What does the list_design_systems tool do? +

Lists all design systems for a given project. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does list_design_systems accept? +

list_design_systems accepts 1 parameter: projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_design_systems? +

Register the 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 Mcp. Nothing to install.

What risk level is list_design_systems? +

list_design_systems is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_design_systems? +

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.

How do I block list_design_systems completely? +

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.

What MCP server provides list_design_systems? +

list_design_systems is provided by the MCP server (https://stitch.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 15 tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →