get_unit
AI agents call get_unit 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 retrieves data from a public energy register without modifying, deleting, or executing operations. The sibling tools are all read-only queries into the MaStR database. Even though the description is empty, the tool name and server context strongly indicate a read operation with no side effects.
From the tool's definition Tool name 'get_unit' combined with sibling tools that are all read-only queries (get_actor, get_catalog_values, search_actors_public, get_location, get_recent_changes). The MaStR is a public energy market register; 'get_unit' retrieves unit/asset information.
Attacks that exploit this kind of access
get_unit. 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 get_unit: 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.
get_unit 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 get_unit 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 get_unit. 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.
get_unit 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 →