stop_strategy · Asterdex MCP: Risk & Policy

WHAT IT DOES

What stop_strategy does on Asterdex

AI agents invoke stop_strategy to trigger actions in Asterdex. 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 stop_strategy needs a policy

This tool executes a command that halts an active trading strategy engine. While not destructive (the strategy itself persists) or financial (no direct money movement), it is an Execute action because it triggers a state change in an external system (the strategy engine) whose effects are immediate and operational.

From the tool's definition Tool name 'stop_strategy' and description 'Stop the running strategy engine' indicate a command that triggers an action affecting the state of an automated trading system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_strategy Rate-limited

stop_strategy 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": {
    "stop_strategy": {
      "limits": [
        {
          "counter": "stop_strategy_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 Asterdex, so you can run agents against it safely.

FAQ

Questions about stop_strategy

What does the stop_strategy tool do? +

Stop the running strategy engine. It is categorised as a Execute tool in the Asterdex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_strategy? +

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

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

Can I rate-limit stop_strategy? +

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

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

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