AI agents call get_usage 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 retrieves documentation for UI components—purely a read operation with no side effects, code execution, data modification, or external operations. The component library context confirms this is for informational purposes to help developers understand how to use components. No blast radius from misuse.
From the tool's definition Tool name 'get_usage' and description 'Get usage documentation for a component' indicate retrieval of informational content without modification or execution.
Documented attack patterns abuse exactly the kind of access get_usage 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 get_usage:
{
"version": "1",
"default": "deny",
"tools": {
"get_usage": {}
}
}get_usage 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.
Get usage documentation for a component. 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 get_usage: 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.
get_usage 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 get_usage 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 get_usage. 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.
get_usage 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.