Get today
AI agents call Get_Current_Production 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 real-time or current solar production metrics from the Tigo Energy system. It performs a data query with no side effects, no code execution, and no irreversible actions. The blast radius of misuse is minimal—an attacker could only access operational visibility data already available to authorized users. Classified as Read with low severity.
From the tool's definition Tool name 'Get_Current_Production' and description 'Get today' indicate retrieval of current production data. Sibling tools all follow read-only patterns (Get_*, retrieve, analytics, monitoring). No mutation, deletion, or execution capabilities are indicated.
Attacks that exploit this kind of access
Get today. 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_Current_Production: 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_Current_Production 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_Current_Production 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_Current_Production. 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_Current_Production 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 →