search_power_consumption_public
AI agents call search_power_consumption_public to retrieve information from MaStR MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to search or retrieve power consumption information from a public energy registry. No side effects, modifications, deletions, or financial transactions are implied. The empty description lowers confidence slightly, but the naming convention and server context strongly suggest a read-only query operation.
From the tool's definition Tool name 'search_power_consumption_public' indicates retrieval of power consumption data. The server is a registry (MaStR) for energy market data, and sibling tools like 'get_*' and 'search_*' are read operations.
Attacks that exploit this kind of access
search_power_consumption_public. It is categorised as a Read tool in the MaStR MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MaStR MCP Server MCP server in PolicyLayer and add a rule for search_power_consumption_public: 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 MaStR MCP Server. Nothing to install.
search_power_consumption_public 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 search_power_consumption_public 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 search_power_consumption_public. 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.
search_power_consumption_public is provided by the MaStR MCP Server MCP server (UliRCS/mastr-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 →