example_update_entity · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What example_update_entity does on MCP Dynamics 365 Commerce Server

AI agents use example_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 example_update_entity needs a policy

This tool creates or modifies data reversibly by updating an entity. It does not delete data (would be Destructive), execute code (would be Execute), or move money (would be Financial). Within a commerce system context, unauthorized entity updates could affect customer records, orders, or pricing, but the changes are typically reversible.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

example_update_entity Rate-limited

example_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": {
    "example_update_entity": {
      "limits": [
        {
          "counter": "example_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 example_update_entity

What does the example_update_entity tool do? +

Update an existing 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 example_update_entity? +

Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for example_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 example_update_entity? +

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

Can I rate-limit example_update_entity? +

Yes. Add a rate_limit block to the example_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 example_update_entity completely? +

Set action: deny in the PolicyLayer policy for example_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 example_update_entity? +

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