AI agents call sg_electricity_history to retrieve information from Sgdata without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical time-series data about electricity generation in Singapore from public government datasets. It performs a read-only query operation with no side effects, data modification capabilities, code execution, or financial implications. The low severity reflects that misuse would only result in unauthorized access to publicly available or non-sensitive historical data.
From the tool's definition Tool name 'sg_electricity_history' and description 'Monthly electricity generation time series for a given source' indicate data retrieval of historical electricity statistics. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
Monthly electricity generation time series for a given source. It is categorised as a Read tool in the Sgdata MCP Server, which means it retrieves data without modifying state.
Register the Sgdata MCP server in PolicyLayer and add a rule for sg_electricity_history: 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 Sgdata. Nothing to install.
sg_electricity_history 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 sg_electricity_history 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 sg_electricity_history. 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.
sg_electricity_history is provided by the Sgdata MCP server (sypherin/sgdata-mcp). 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 →