customer_update_entity

WHAT IT DOES

What customer_update_entity does on MCP Dynamics 365 Commerce Server

AI agents use customer_update_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 IT NEEDS A POLICY

Why customer_update_entity needs a policy

This tool modifies customer data reversibly through an update operation. While it doesn't delete data (which would be Destructive) or move money (Financial), updating customer entities in a commerce system could affect business operations—customer profiles influence orders, pricing, communications, and financial records.

From the tool's definition Tool name contains 'update' and description states 'Update an existing customer entity', indicating modification of existing data in a customer management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

customer_update_entity Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "customer_update_entity": {
      "limits": [
        {
          "counter": "customer_update_entity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Dynamics 365 Commerce Server, so you can run agents against it safely.

FAQ

Questions about customer_update_entity

What does the customer_update_entity tool do? +

Update an existing 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.

How do I enforce a policy on customer_update_entity? +

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

What risk level is customer_update_entity? +

customer_update_entity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit customer_update_entity? +

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

How do I block customer_update_entity completely? +

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

What MCP server provides customer_update_entity? +

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