Low Risk

list_catalyst_components

List all 28 available Catalyst UI components organized by category. Categories include: forms (button, checkbox, fieldset, input, radio, select, switch, textarea), navigation (navbar, sidebar, dropdown, link), layout (divider, heading, stacked-layout, auth-layout), feedback (alert, badge, dialog)...

Part of the Next Js Tailwind Assistant MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call list_catalyst_components to retrieve information from Next Js Tailwind Assistant without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though list_catalyst_components only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

caullenomdahl-nextjs-react-tailwind-assistant.yaml
tools:
  list_catalyst_components:
    rules:
      - action: allow

See the full Next Js Tailwind Assistant policy for all 16 tools.

Tool Name list_catalyst_components
Category Read
Risk Level Low

View all 16 tools →

Agents calling read-class tools like list_catalyst_components have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the list_catalyst_components tool do? +

List all 28 available Catalyst UI components organized by category. Categories include: forms (button, checkbox, fieldset, input, radio, select, switch, textarea), navigation (navbar, sidebar, dropdown, link), layout (divider, heading, stacked-layout, auth-layout), feedback (alert, badge, dialog), data-display (avatar, description-list, listbox, pagination, table, text), and advanced (combobox).. It is categorised as a Read tool in the Next Js Tailwind Assistant MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_catalyst_components? +

Add a rule in your Intercept YAML policy under the tools section for list_catalyst_components. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Next Js Tailwind Assistant MCP server.

What risk level is list_catalyst_components? +

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

Can I rate-limit list_catalyst_components? +

Yes. Add a rate_limit block to the list_catalyst_components rule in your Intercept 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_catalyst_components completely? +

Set action: deny in the Intercept policy for list_catalyst_components. 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_catalyst_components? +

list_catalyst_components is provided by the Next Js Tailwind Assistant MCP server (CaullenOmdahl/nextjs-react-tailwind-assistant). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Next Js Tailwind Assistant

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.