manage_stream · Asterdex MCP: Risk & Policy

WHAT IT DOES

What manage_stream does on Asterdex

AI agents invoke manage_stream 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 manage_stream needs a policy

Managing WebSocket streams involves establishing, modifying, or terminating persistent connections and triggering external operations. While primarily infrastructure-oriented, it executes actions that affect real-time data pipelines. In the context of a trading server, disrupting or manipulating streams could indirectly affect trading operations.

From the tool's definition Manage WebSocket streams for real-time data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_stream Rate-limited

manage_stream 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": {
    "manage_stream": {
      "limits": [
        {
          "counter": "manage_stream_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 manage_stream

What does the manage_stream tool do? +

Manage WebSocket streams for real-time data. 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 manage_stream? +

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

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

Can I rate-limit manage_stream? +

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

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

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