Gets categories by OData query.
AI agents call categories_get_categories to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves product or entity categories from the Dynamics 365 Commerce system without modifying, deleting, or executing any operations. OData queries are typically used for data retrieval. The blast radius of misuse is minimal—an AI agent could only retrieve data it shouldn't see, not modify or destroy anything.
From the tool's definition Tool name 'categories_get_categories' and description 'Gets categories by OData query' indicate a retrieval operation with no side effects. The verb 'gets' and the use of OData query (standard for read-only queries) confirm this is a read operation.
Attacks that exploit this kind of access
Gets categories by OData query. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for categories_get_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 MCP Dynamics 365 Commerce Server. Nothing to install.
categories_get_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 categories_get_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 categories_get_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.
categories_get_categories is provided by the MCP Dynamics 365 Commerce Server MCP server (jiantmo/mcp-commerce). 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 →