sync_order · Basis MCP Server MCP: Risk & Policy

WHAT IT DOES

What sync_order does on Basis MCP Server

AI agents invoke sync_order to trigger actions in Basis MCP 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 sync_order needs a policy

Syncing an order book transaction involves triggering an on-chain or protocol-level operation to reconcile/update order state. This is an external execution action rather than a simple read or write, as it affects the state of live trading infrastructure. However, the description is vague and does not confirm irreversible destruction or direct financial movement, so confidence is moderate.

From the tool's definition 'Sync an order book transaction' — triggers an external operation on the order book

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_order Rate-limited

sync_order 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": {
    "sync_order": {
      "limits": [
        {
          "counter": "sync_order_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 Basis MCP Server, so you can run agents against it safely.

FAQ

Questions about sync_order

What does the sync_order tool do? +

Sync an order book transaction. It is categorised as a Execute tool in the Basis MCP 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 sync_order? +

Register the Basis MCP Server MCP server in PolicyLayer and add a rule for sync_order: 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 Basis MCP Server. Nothing to install.

What risk level is sync_order? +

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

Can I rate-limit sync_order? +

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

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

sync_order is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.