Health check: fetch components live and report count + latency
AI agents call mui_health to retrieve information from MUI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The mui_health tool performs a health check by fetching component data and reporting metrics (count and latency). This is a read-only operation that queries the state of components to provide diagnostic information. It has no side effects, does not modify data, does not execute code, and does not involve financial transactions.
From the tool's definition Tool description states 'fetch components live and report count + latency' — a monitoring/diagnostic operation that retrieves status information without modifying or executing external operations.
Attacks that exploit this kind of access
Health check: fetch components live and report count + latency. It is categorised as a Read tool in the MUI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MUI MCP Server MCP server in PolicyLayer and add a rule for mui_health: 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 MUI MCP Server. Nothing to install.
mui_health 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 mui_health 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 mui_health. 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.
mui_health is provided by the MUI MCP Server MCP server (tejas-borate-wai/mui-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →