customer_create_entity
Create a new customer entity
This record as markdown: /tools/jiantmo-mcp-commerce/customer-create-entity.md
What customer_create_entity does on MCP Dynamics 365 Commerce Server
AI agents use customer_create_entity to create or update resources in MCP Dynamics 365 Commerce Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Dynamics 365 Commerce Server environment.
Why customer_create_entity is rated Medium
This tool creates new customer data in a production-like Dynamics 365 Commerce system. While creation is reversible (unlike deletion), it modifies the database by adding records, placing it in the Write category.
From the tool's definition Tool name 'customer_create_entity' explicitly uses the verb 'create' and description states 'Create a new customer entity', indicating irreversible creation of customer records in a commerce system.
Attacks that exploit this kind of access
The rule that runs customer_create_entity 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 customer_create_entity, this is the rule to start with:
customer_create_entity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 customer_create_entity call is checked against it from then on.
Questions about customer_create_entity
Create a new customer entity. It is categorised as a Write tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for customer_create_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.
customer_create_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the customer_create_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 customer_create_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.
customer_create_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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue