AI agents call get-health-check-group-by-name to retrieve information from Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves health check group information for monitoring purposes. The use of 'get' and 'details' indicate a read-only query operation that returns data about system health status without modifying any state or triggering actions. The context of 'system monitoring' further confirms this is a passive information retrieval function, placing it squarely in the Read category with low severity risk.
From the tool's definition Tool name includes 'get-' prefix and description states 'Gets specific health check group details by name' with 'no side effects' implied by retrieval semantics. Returns system monitoring data without modification.
Attacks that exploit this kind of access
Gets specific health check group details by name for system monitoring. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for get-health-check-group-by-name: 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 Mcp Dev. Nothing to install.
get-health-check-group-by-name 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-health-check-group-by-name 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-health-check-group-by-name. 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-health-check-group-by-name is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). 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 →