Get overall system health summary.
AI agents call get_system_health_summary to retrieve information from MCP Log Analyzer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval of system health information. It queries existing system state and returns a summary, with no side effects, no code execution, no data modification, and no destructive capabilities. The low severity reflects minimal risk even if called unexpectedly by an agent, as it only gathers diagnostic information.
From the tool's definition Tool name is 'get_system_health_summary' and description states it retrieves 'overall system health summary' — a query operation that reads and returns data about system status without modifying or executing anything.
Attacks that exploit this kind of access
Get overall system health summary. It is categorised as a Read tool in the MCP Log Analyzer MCP Server, which means it retrieves data without modifying state.
Register the MCP Log Analyzer MCP server in PolicyLayer and add a rule for get_system_health_summary: 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 Log Analyzer. Nothing to install.
get_system_health_summary 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_summary 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_summary. 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_summary is provided by the MCP Log Analyzer MCP server (sedwardstx/demomcp). 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 →