get_portfolio_value
AI agents call get_portfolio_value to retrieve information from Hyperliquid MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves portfolio valuation information without modifying, executing external operations, or committing financial transactions. It is a passive query operation similar to other 'get_' prefixed tools in the Hyperliquid MCP server. The lack of action verbs suggesting mutation or side effects, combined with the Read-category naming pattern, strongly indicates this is a data retrieval function.
From the tool's definition Tool name 'get_portfolio_value' indicates a data retrieval operation. The prefix 'get_' and sibling tools like 'get_candles', 'get_funding_rates', and 'get_historical_orders' are all Read operations.
Attacks that exploit this kind of access
get_portfolio_value. It is categorised as a Read tool in the Hyperliquid MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hyperliquid MCP Server MCP server in PolicyLayer and add a rule for get_portfolio_value: 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.
get_portfolio_value is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_portfolio_value 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 get_portfolio_value. 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.
get_portfolio_value is provided by the Hyperliquid MCP Server MCP server (jhonatanpinheiro/hyperliquid-mcp-server). 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 →