Get complete wallet portfolio using Zerion API
AI agents call get_wallet_portfolio to retrieve information from Odos 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 wallet portfolio information without modifying, executing, or deleting anything. It is a read-only operation. Severity is medium rather than low because portfolio data exposure could inform targeted attacks (phishing, social engineering, fund theft) if an attacker gains access to sensitive wallet information, but the tool itself performs no destructive action.
From the tool's definition Tool name is 'get_wallet_portfolio' and description states 'Get complete wallet portfolio using Zerion API' — this is a retrieval operation with no side effects. The verb 'get' and the passive construction 'using API' indicate data querying only.
Attacks that exploit this kind of access
Get complete wallet portfolio using Zerion API. It is categorised as a Read tool in the Odos MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odos MCP Server MCP server in PolicyLayer and add a rule for get_wallet_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 Odos MCP Server. Nothing to install.
get_wallet_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_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_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_portfolio is provided by the Odos MCP Server MCP server (odos-xyz/odos-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 →