Return health status of all MCP servers and aggregate metrics.
AI agents call get_system_health to retrieve information from MCPDischarge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns health/status information about MCP servers and metrics. It performs only data retrieval with no modifications, deletions, or external operations. It is a read-only monitoring function. While it operates in a healthcare context (MCPDischarge), the tool itself does not access, modify, or delete PHI, financial data, or pharmacy records—it only reports system infrastructure health.
From the tool's definition Tool name 'get_system_health' and description 'Return health status of all MCP servers and aggregate metrics' indicate a query operation that retrieves system monitoring data with no side effects.
Attacks that exploit this kind of access
Return health status of all MCP servers and aggregate metrics. It is categorised as a Read tool in the MCPDischarge MCP Server, which means it retrieves data without modifying state.
Register the MCPDischarge MCP server in PolicyLayer and add a rule for get_system_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 MCPDischarge. Nothing to install.
get_system_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 get_system_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 get_system_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.
get_system_health is provided by the MCPDischarge MCP server (prashantsingh1234/mcp_project). 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 →