List all available MaStR catalog categories with their IDs.
AI agents call get_catalog_categories 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 and lists catalog metadata (categories and IDs) from the German energy market register. It performs a read-only query operation with no capability to modify, delete, or execute arbitrary actions. The low severity reflects minimal blast radius if misused—an agent could at worst retrieve public catalog information that is likely already documented or accessible through normal channels.
From the tool's definition Tool name is 'get_catalog_categories' and description states 'List all available MaStR catalog categories with their IDs' - a pure retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List all available MaStR catalog categories with their IDs. 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_catalog_categories: 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_catalog_categories 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_catalog_categories 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_catalog_categories. 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_catalog_categories 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 →