New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

create_design_system_from_design_md

Creates a design system for a project, with user uploaded DESIGN.md file, and displays the design system in the UI. Instructions for Tool Call: * Should call upload_design_md tool first to upload DESIGN.md to a Stitch project.

SERVERMcp SOURCEhttps://stitch.googleapis.com/mcp
Medium RISK CLASS
Category Write
Parameters 32 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-stitch-mcp/create-design-system-from-design-md.md

What create_design_system_from_design_md does on Mcp

AI agents use create_design_system_from_design_md to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.

ParameterTypeRequiredDescription
projectId string Yes Required. The project ID to update design system for, example: '4044680601076201931', without the `projects/` prefix.
deviceType string Optional. The device type of the screen.
selectedScreenInstance object Yes Required. The screen instance to create the design system from, which is created by UploadDesignMd RPC.

Parameters from the server's own tool schema.

Why create_design_system_from_design_md is rated Medium

This tool creates and persists a new design system resource within a Stitch project. It is reversible (design systems can typically be modified or deleted), so it does not qualify as Destructive. It does not execute arbitrary code or external operations (Execute), nor does it move money (Financial).

From the tool's definition The tool description states it 'Creates a design system' which is a create/write operation. The instructions indicate it uploads a file and modifies project state by creating a new design system artifact.

Questions about create_design_system_from_design_md

What does the create_design_system_from_design_md tool do? +

Creates a design system for a project, with user uploaded DESIGN.md file, and displays the design system in the UI. Instructions for Tool Call: * Should call upload_design_md tool first to upload DESIGN.md to a Stitch project. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_design_system_from_design_md accept? +

create_design_system_from_design_md accepts 3 parameters: projectId, deviceType, selectedScreenInstance. Required: projectId, selectedScreenInstance. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_design_system_from_design_md? +

Register the MCP server in PolicyLayer and add a rule for create_design_system_from_design_md: 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 create_design_system_from_design_md? +

create_design_system_from_design_md is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_design_system_from_design_md? +

Yes. Add a rate_limit block to the create_design_system_from_design_md 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 create_design_system_from_design_md completely? +

Set action: deny in the PolicyLayer policy for create_design_system_from_design_md. 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 create_design_system_from_design_md? +

create_design_system_from_design_md 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.

More on , and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.