catalogs_get_catalogs
Gets catalogs by OData query.
This record as markdown: /tools/jiantmo-mcp-commerce/catalogs-get-catalogs.md
What catalogs_get_catalogs does on MCP Dynamics 365 Commerce Server
AI agents call catalogs_get_catalogs to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why catalogs_get_catalogs is rated Low
This tool queries and retrieves catalog data without side effects. The 'get' verb and query-based retrieval pattern are characteristic of Read operations. No data is created, modified, deleted, or executed. The severity is low as it merely accesses existing data with minimal risk if misused.
From the tool's definition Tool name 'catalogs_get_catalogs' and description 'Gets catalogs by OData query' indicate a retrieval operation with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs catalogs_get_catalogs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Dynamics 365 Commerce Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For catalogs_get_catalogs, this is the rule to start with:
catalogs_get_catalogs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every catalogs_get_catalogs call is checked against it from then on.
Questions about catalogs_get_catalogs
Gets catalogs 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 catalogs_get_catalogs: 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.
catalogs_get_catalogs 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 catalogs_get_catalogs 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 catalogs_get_catalogs. 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.
catalogs_get_catalogs 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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue