set_stop_loss · HyperLiquid MCP Server MCP: Risk & Policy

WHAT IT DOES

What set_stop_loss does on HyperLiquid MCP Server

AI agents use set_stop_loss to create or update resources in HyperLiquid MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HyperLiquid MCP Server environment.

WHY IT NEEDS A POLICY

Why set_stop_loss needs a policy

An AI agent can call set_stop_loss faster than any human can review — one bad instruction and it creates or modifies resources in HyperLiquid MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_stop_loss Rate-limited

set_stop_loss stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_stop_loss": {
      "limits": [
        {
          "counter": "set_stop_loss_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about set_stop_loss

What does the set_stop_loss tool do? +

set_stop_loss. It is categorised as a Write tool in the HyperLiquid MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_stop_loss? +

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

What risk level is set_stop_loss? +

set_stop_loss is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_stop_loss? +

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

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

set_stop_loss is provided by the HyperLiquid MCP Server MCP server (talkincode/hyperliquid-mcp-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.