Get list of all Storybook stories
AI agents call storybook_get_stories to retrieve information from UI/UX MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves Storybook story metadata. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal — an agent might retrieve component documentation or story information unnecessarily, but no data can be damaged, modified, or financial impact incurred.
From the tool's definition Tool name and description indicate it 'Get[s] list of all Storybook stories' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get list of all Storybook stories. It is categorised as a Read tool in the UI/UX MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UI/UX MCP Server MCP server in PolicyLayer and add a rule for storybook_get_stories: 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 UI/UX MCP Server. Nothing to install.
storybook_get_stories 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 storybook_get_stories 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 storybook_get_stories. 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.
storybook_get_stories is provided by the UI/UX MCP Server MCP server (willem4130/ui-ux-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 →