execute_order · Asterdex MCP: Risk & Policy

WHAT IT DOES

What execute_order does on Asterdex

AI agents use execute_order to commit financial operations through Asterdex — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why execute_order needs a policy

This tool directly executes financial trades (perpetual futures orders) on a DEX, committing real financial obligations. Misuse by an AI agent could result in significant monetary losses through unintended trades, wrong position sizes, or market manipulation. Financial is the highest severity category and clearly applies here.

From the tool's definition "Place a new order or modify a position" on a DEX perpetual futures trading server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_order Approval-gated

Any call to execute_order is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_order": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Asterdex, so you can run agents against it safely.

FAQ

Questions about execute_order

What does the execute_order tool do? +

Place a new order or modify a position. It is categorised as a Financial tool in the Asterdex MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on execute_order? +

Register the Asterdex MCP server in PolicyLayer and add a rule for execute_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 Asterdex. Nothing to install.

What risk level is execute_order? +

execute_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit execute_order? +

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

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

execute_order is provided by the Asterdex MCP server (tyranosurasmax/asterdex-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.