AI agents call get_account_info to retrieve information from Asterdex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves sensitive financial information (balances, positions, orders, liquidation history, PnL) but performs no side effects. It is categorized as Read. Severity is medium rather than low because the retrieved data is sensitive financial information that could be misused if exposed to an unauthorized agent, but the tool itself causes no direct financial harm or irreversible changes.
From the tool's definition Tool name 'get_account_info' and description 'Get account details: balances, positions, orders, ADL risk, liquidation history, or PnL' — uses 'Get' verb and describes only retrieval of financial account data with no modification, creation, or deletion.
Attacks that exploit this kind of access
Get account details: balances, positions, orders, ADL risk, liquidation history, or PnL. It is categorised as a Read tool in the Asterdex MCP Server, which means it retrieves data without modifying state.
Register the Asterdex MCP server in PolicyLayer and add a rule for get_account_info: 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.
get_account_info 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_account_info 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_account_info. 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_account_info 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.
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 →