Get recent alerts and system health information from Tigo system.
AI agents call Get_System_Alerts 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 retrieves system alerts and health status information from a solar monitoring system. There are no side effects, no data modification, no code execution, and no financial impact. Even if an AI agent misuses this tool by requesting alerts repeatedly, the worst case is excessive API calls or information disclosure about system status—neither of which causes damage.
From the tool's definition Tool name 'Get_System_Alerts' and description 'Get recent alerts and system health information' both indicate data retrieval with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get recent alerts and system health information 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_Alerts: 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_Alerts 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_Alerts 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_Alerts. 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_Alerts 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 →