New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cart_get_entity_by_key

Get cart entity by key

SERVERMCP Dynamics 365 Commerce Server SOURCEjiantmo/mcp-commerce
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jiantmo-mcp-commerce/cart-get-entity-by-key.md

What cart_get_entity_by_key does on MCP Dynamics 365 Commerce Server

AI agents call cart_get_entity_by_key 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 cart_get_entity_by_key is rated Low

This tool retrieves cart data by a key identifier without any side effects, modifications, or deletions. It is a straightforward read operation that queries existing cart information in the Dynamics 365 Commerce system. No data is created, modified, or deleted, making it a low-severity read operation.

From the tool's definition Tool name 'cart_get_entity_by_key' and description 'Get cart entity by key' indicate a retrieval operation with no modification capability. The 'get' verb and read-only nature confirm this is a query operation.

Questions about cart_get_entity_by_key

What does the cart_get_entity_by_key tool do? +

Get cart entity by key. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cart_get_entity_by_key? +

Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for cart_get_entity_by_key: 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.

What risk level is cart_get_entity_by_key? +

cart_get_entity_by_key is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cart_get_entity_by_key? +

Yes. Add a rate_limit block to the cart_get_entity_by_key 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.

How do I block cart_get_entity_by_key completely? +

Set action: deny in the PolicyLayer policy for cart_get_entity_by_key. 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.

What MCP server provides cart_get_entity_by_key? +

cart_get_entity_by_key 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Dynamics 365 Commerce Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.