execute_spot_order · Asterdex MCP: Risk & Policy

WHAT IT DOES

What execute_spot_order does on Asterdex

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

This tool places real buy/sell orders on a decentralized exchange, committing financial transactions. Misuse by an AI agent could result in unintended purchases or sales of assets, causing direct financial loss. As a trade execution tool on a financial platform, it falls squarely in the Financial category with critical severity.

From the tool's definition "Place a spot order: market buy/sell or limit order" — directly executes financial trades on a DEX

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_spot_order Approval-gated

Any call to execute_spot_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_spot_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_spot_order

What does the execute_spot_order tool do? +

Place a spot order: market buy/sell or limit order. 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_spot_order? +

Register the Asterdex MCP server in PolicyLayer and add a rule for execute_spot_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_spot_order? +

execute_spot_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_spot_order? +

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

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

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