search_actors_soap
AI agents call search_actors_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.
This tool appears to search for actors (entities) in the MaStR register using SOAP protocol. Despite empty description, the naming pattern and context of sibling read-only tools strongly suggest this retrieves data without side effects. No write, delete, execution, or financial capability is evident. The tool fits the Read category as it queries data from a government energy market register.
From the tool's definition Tool name 'search_actors_soap' combined with sibling tools like 'get_actor', 'get_grid_connection', 'get_location', 'get_catalog_values' that are all read operations on a public energy market register. The 'search_actors' prefix indicates querying/retrieval.
Attacks that exploit this kind of access
search_actors_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_actors_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_actors_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_actors_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_actors_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_actors_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 →