Get comprehensive statistics about the OriginUI component registry
AI agents call get_registry_stats to retrieve information from OriginUI 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 statistical information about a component registry. It is a read-only query operation that has no side effects, does not modify data, does not execute code, and does not delete anything. The blast radius of misuse is minimal—an AI agent could at worst retrieve redundant registry statistics. Consistent with sibling tools like list_components and search_components, which are also Read operations.
From the tool's definition Tool name 'get_registry_stats' and description 'Get comprehensive statistics about the OriginUI component registry' indicate a query operation that retrieves aggregated data without modifying or executing anything.
Documented attack patterns abuse exactly the kind of access get_registry_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OriginUI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_registry_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_registry_stats": {}
}
}get_registry_stats 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 comprehensive statistics about the OriginUI component registry. It is categorised as a Read tool in the OriginUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OriginUI MCP Server MCP server in PolicyLayer and add a rule for get_registry_stats: 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 OriginUI MCP Server. Nothing to install.
get_registry_stats 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_registry_stats 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_registry_stats. 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_registry_stats is provided by the OriginUI MCP Server MCP server (kelvinchng/origin-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OriginUI 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 OriginUI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.