List all available Basecoat components organized by category
AI agents call list_components to retrieve information from Basecoat UI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns metadata about available UI components. It does not create, modify, delete, or execute any code. The blast radius of misuse is minimal since an AI agent calling this tool can only retrieve a list of component names and categories, with no ability to affect system state or data.
From the tool's definition Tool name is 'list_components' and description states it 'List all available Basecoat components organized by category' — a pure retrieval operation with no side effects, modifications, or execution.
Documented attack patterns abuse exactly the kind of access list_components gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Basecoat UI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_components:
{
"version": "1",
"default": "deny",
"tools": {
"list_components": {}
}
}list_components is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all available Basecoat components organized by category. It is categorised as a Read tool in the Basecoat UI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basecoat UI MCP Server MCP server in PolicyLayer and add a rule for list_components: 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 Basecoat UI MCP Server. Nothing to install.
list_components 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 list_components 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 list_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.
list_components is provided by the Basecoat UI MCP Server MCP server (sorbh/basecoat-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Basecoat UI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Basecoat UI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.