Get comprehensive system health status combining multiple data sources from Tigo system.
AI agents call Get_System_Health to retrieve information from Tigo Energy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves system health information from the Tigo solar monitoring system. It performs data aggregation from multiple sources but does not modify, create, delete, or execute any operations.
From the tool's definition Get_System_Health retrieves comprehensive system health status combining multiple data sources - described as a GET operation that aggregates existing monitoring data without modification, creation, or deletion.
Attacks that exploit this kind of access
Get comprehensive system health status combining multiple data sources from Tigo system. It is categorised as a Read tool in the Tigo Energy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tigo Energy MCP Server 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 Tigo Energy MCP Server. 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 Tigo Energy MCP Server MCP server (matt-dreyer/tigo_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 →