Create a new trading account with real Hyperliquid execution. Provide your HL wallet address and signing key (API Agent Wallet private key) for live trading. Trades execute on YOUR Hyperliquid account — we never hold your funds. Sign up via https://app.hyperliquid.xyz/join/PF for referral benefits.
AI agents use trading_register to commit financial operations through Purple Flea Trading — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool registers a live trading account and requires submission of a private key/signing key, enabling real financial trades on Hyperliquid. It directly facilitates financial operations (perpetual futures trading with up to 50x leverage) and exposure of a private key could allow full account compromise.
From the tool's definition Create a new trading account with real Hyperliquid execution. Provide your HL wallet address and signing key (API Agent Wallet private key) for live trading. Trades execute on YOUR Hyperliquid account
Attacks that exploit this kind of access
Create a new trading account with real Hyperliquid execution. Provide your HL wallet address and signing key (API Agent Wallet private key) for live trading. Trades execute on YOUR Hyperliquid account — we never hold your funds. Sign up via https://app.hyperliquid.xyz/join/PF for referral benefits. It is categorised as a Financial tool in the Purple Flea Trading MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Purple Flea Trading MCP server in PolicyLayer and add a rule for trading_register: 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 Purple Flea Trading. Nothing to install.
trading_register is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the trading_register 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.
Set action: deny in the PolicyLayer policy for trading_register. 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.
trading_register is provided by the Purple Flea Trading MCP server (purple-flea/agent-trading). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →