storybook_create_component · Storybook MCP: Risk & Policy

WHAT IT DOES

What storybook_create_component does on Storybook

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

WHY IT NEEDS A POLICY

Why storybook_create_component needs a policy

This tool creates new components in Storybook, a reversible write operation. The empty description lowers confidence slightly, but the name and sibling tools (which include list and get operations) confirm it modifies the component registry. Not Destructive because creation is not irreversible (components can be deleted separately).

From the tool's definition Tool name 'storybook_create_component' indicates creation of a component artifact. While the description is empty, the verb 'create' and the context of a Storybook integration (which manages UI component definitions and stories) imply the tool writes/creates…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

storybook_create_component Rate-limited

storybook_create_component stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "storybook_create_component": {
      "limits": [
        {
          "counter": "storybook_create_component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Storybook, so you can run agents against it safely.

FAQ

Questions about storybook_create_component

What does the storybook_create_component tool do? +

storybook_create_component. It is categorised as a Write tool in the Storybook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on storybook_create_component? +

Register the Storybook MCP server in PolicyLayer and add a rule for storybook_create_component: 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 Storybook. Nothing to install.

What risk level is storybook_create_component? +

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

Can I rate-limit storybook_create_component? +

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

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

storybook_create_component is provided by the Storybook MCP server (stevebrownlee/storybook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.