appinfo_update_application_version

WHAT IT DOES

What appinfo_update_application_version does on MCP Dynamics 365 Commerce Server

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

This tool creates or modifies data (application version) reversibly on a POS device. It is not a read operation (no retrieval), not destructive (updates are typically reversible and don't permanently delete data), not execute (doesn't run arbitrary code/commands based on arguments), and not financial.

From the tool's definition Tool name 'appinfo_update_application_version' and description 'Updates the POS device' indicate modification of application/device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

appinfo_update_application_version Rate-limited

appinfo_update_application_version 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": {
    "appinfo_update_application_version": {
      "limits": [
        {
          "counter": "appinfo_update_application_version_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 appinfo_update_application_version

What does the appinfo_update_application_version tool do? +

Updates the POS device. 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 appinfo_update_application_version? +

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

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

Can I rate-limit appinfo_update_application_version? +

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

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

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

// THE FULL RECORD

appinfo_update_application_version is one line of MCP Dynamics 365 Commerce Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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