search_gas_consumption_soap
AI agents call search_gas_consumption_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 MaStR server is an energy market registry providing data access. Search and retrieval operations on such public registers are Read operations. The empty description lowers confidence slightly, but the naming convention and context of sibling tools strongly suggest this is a data retrieval tool with no side effects.
From the tool's definition Tool name 'search_gas_consumption' indicates a search/query operation; description is empty but sibling tools like 'get_actor', 'get_balancing_areas', 'get_catalog_values', and 'get_location' are all Read-category retrieval operations, suggesting this tool…
Attacks that exploit this kind of access
search_gas_consumption_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_gas_consumption_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_gas_consumption_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_gas_consumption_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_gas_consumption_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_gas_consumption_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 →