Get Tigo system data for a specific date range with configurable granularity.
AI agents call Get_Data_Range 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 solar system analytics and monitoring data within a specified date range. It performs no mutations, deletions, or external operations. The configurable granularity parameter allows filtering but does not alter underlying data. Misuse would at worst expose historical solar production metrics, a low-sensitivity information type with no destructive or financial impact.
From the tool's definition Tool name 'Get_Data_Range' and description 'Get Tigo system data for a specific date range' indicate retrieval of historical data. The verb 'Get' and lack of modification language confirm read-only behavior.
Attacks that exploit this kind of access
Get Tigo system data for a specific date range with configurable granularity. 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_Data_Range: 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_Data_Range 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_Data_Range 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_Data_Range. 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_Data_Range 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 →