Check the health status of the enhanced MCP server
AI agents call get_health_status to retrieve information from MCP MAGMA Handbook Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a diagnostic tool that queries the current health/status of the server. It retrieves information with no side effects, making it a Read category tool. Severity is low because even if misused, it only exposes non-sensitive operational status and does not enable any harmful actions.
From the tool's definition Tool name 'get_health_status' and description 'Check the health status of the enhanced MCP server' indicate a read-only diagnostic operation that retrieves status information without modifying, executing, or affecting system state.
Attacks that exploit this kind of access
Check the health status of the enhanced MCP server. It is categorised as a Read tool in the MCP MAGMA Handbook Server MCP Server, which means it retrieves data without modifying state.
Register the MCP MAGMA Handbook Server MCP server in PolicyLayer and add a rule for get_health_status: 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 MAGMA Handbook Server. Nothing to install.
get_health_status 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_status 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_status. 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_status is provided by the MCP MAGMA Handbook Server MCP server (legenai/mcp-magma-handbook). 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 →