markOrderAsPaid

What markOrderAsPaid does on Bybit MCP Server

AI agents use markOrderAsPaid to create or update resources in Bybit MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bybit MCP Server environment.

Why markOrderAsPaid is rated Medium

This tool modifies data (order status) in a cryptocurrency exchange's P2P trading system. It is Write rather than Financial because it updates a transaction record rather than moving funds directly, but it has high severity because misuse could mark fraudulent or unintended orders as paid, potentially triggering fund transfers or affecting trading settlement.

From the tool's definition markOrderAsPaid marks a P2P order as paid, updating the order's status irreversibly from unpaid to paid state. While the description is incomplete (ends with 'Note: \'), the tool name and context indicate state modification of a financial transaction record.

The rule that runs markOrderAsPaid safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For markOrderAsPaid, this is the rule to start with:

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

Questions about markOrderAsPaid