// MCP TOOL REFERENCE

PETAL COMPONENTS MCP TOOLS

3 tools from the Petal Components Mcp MCP Server, categorised by risk level.

View the Petal Components Mcp policy → Token cost: 353 tokens →

// ALL 3 PETAL COMPONENTS MCP TOOLS

READ 3 tools

Read get_component Get the full schema for one petal_components component: attrs, slots, defaults, allowed values, and a worki... Read get_install_instructions Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks ... Read list_components List every component shipped by petal_components, the shadcn-style component library for Phoenix LiveView. ...

// RUNNING THIS SERVER

The managed route: connect Petal Components Mcp through the PolicyLayer gateway — every tool call above is checked against your policy before it runs, with a full audit log.

DIRECT INSTALL (UNMANAGED) npx -y petal-components-mcp

// FAQ

How many tools does the Petal Components Mcp MCP server have? +

The Petal Components Mcp MCP server exposes 3 tools across 1 categories: Read.

How do I enforce policies on Petal Components Mcp tools? +

Route the Petal Components Mcp server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Petal Components Mcp tools fall into? +

Petal Components Mcp tools are categorised as Read (3). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.