AI agents call get_wallet_set_portfolio to retrieve information from Zerion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial data (portfolio overview) across multiple wallets without creating, modifying, or deleting any data. It performs a read-only query operation. Severity is medium rather than low because exposing detailed portfolio/balance information could enable reconnaissance attacks or inform targeted social engineering, though the data itself cannot be directly harmed by misuse of this read operation.
From the tool's definition Tool name 'get_wallet_set_portfolio' and description 'Get portfolio overview for a set of wallets (multi-wallet aggregation)' indicate a retrieval operation that queries and aggregates wallet portfolio data without modifying or executing actions.
Attacks that exploit this kind of access
Get portfolio overview for a set of wallets (multi-wallet aggregation). It is categorised as a Read tool in the Zerion MCP Server, which means it retrieves data without modifying state.
Register the Zerion MCP server in PolicyLayer and add a rule for get_wallet_set_portfolio: 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 Zerion. Nothing to install.
get_wallet_set_portfolio 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_wallet_set_portfolio 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_wallet_set_portfolio. 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_wallet_set_portfolio is provided by the Zerion MCP server (rockyale/zerion-mcp). 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 →