async_service_post_offline_transactions

WHAT IT DOES

What async_service_post_offline_transactions does on MCP Dynamics 365 Commerce Server

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

The 'post' operation modifies commerce transaction data by creating or committing offline transaction records to the system. This is a Write action (creates/records data reversibly) rather than Destructive since transactions can typically be voided or adjusted.

From the tool's definition Tool name 'async_service_post_offline_transactions' with description 'Posts offline transactions' indicates creation/submission of transaction records in a commerce system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

async_service_post_offline_transactions Rate-limited

async_service_post_offline_transactions 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": {
    "async_service_post_offline_transactions": {
      "limits": [
        {
          "counter": "async_service_post_offline_transactions_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 async_service_post_offline_transactions

What does the async_service_post_offline_transactions tool do? +

Posts offline transactions. 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 async_service_post_offline_transactions? +

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

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

Can I rate-limit async_service_post_offline_transactions? +

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

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

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