shifts_blind_close · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What shifts_blind_close does on MCP Dynamics 365 Commerce Server

AI agents invoke shifts_blind_close to trigger actions in MCP Dynamics 365 Commerce Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why shifts_blind_close needs a policy

Blind closing a shift in a retail POS system finalizes the shift without a cash count reconciliation. This is an irreversible operational action that affects financial audit trails, shift records, and cash management.

From the tool's definition 'Blind close a shift' — closing a shift is a significant operational action in retail/commerce (finalizing a POS shift without counting the drawer), which triggers external operations in Dynamics 365 Commerce and has lasting effects on financial records and…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shifts_blind_close Rate-limited

shifts_blind_close stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shifts_blind_close": {
      "limits": [
        {
          "counter": "shifts_blind_close_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 shifts_blind_close

What does the shifts_blind_close tool do? +

Blind close a shift. It is categorised as a Execute tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on shifts_blind_close? +

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

shifts_blind_close is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit shifts_blind_close? +

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

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

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