search_power_generation_soap
AI agents call search_power_generation_soap 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 naming convention and context strongly indicate this tool retrieves or queries power generation data from the MaStR registry. No evidence of modification, deletion, execution, or financial operations. The 'search' prefix combined with an empty description lowers confidence slightly, but the server's domain (energy market register) and sibling tool patterns support a Read classification.
From the tool's definition Tool name contains 'search_power_generation' suggesting a query/retrieval operation on MaStR energy register data.
Attacks that exploit this kind of access
search_power_generation_soap. 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_generation_soap: 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_generation_soap 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_generation_soap 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_generation_soap. 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_generation_soap 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 →