Delete an entity
AI agents call example_delete_entity to permanently remove resources in MCP Dynamics 365 Commerce Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes data without possibility of recovery. This is an irreversible operation on commerce data (customers, orders, products, or other entities in Dynamics 365). High severity due to potential data loss in a production system. Confidence is high despite minimal description because 'delete' is unambiguous.
From the tool's definition Tool name 'example_delete_entity' with description 'Delete an entity' explicitly performs deletion, an irreversible operation that cannot be undone.
Attacks that exploit this kind of access
Delete an entity. It is categorised as a Destructive tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for example_delete_entity: 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.
example_delete_entity is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the example_delete_entity 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 example_delete_entity. 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.
example_delete_entity 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 →