AI agents call get_portfolio to retrieve information from Zapper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries financial data from a blockchain wallet without creating, modifying, deleting, or executing any transactions. It is purely informational, showing current state of assets. While the data retrieved has financial significance, the tool itself performs no financial transactions, fund movements, or irreversible actions.
From the tool's definition Tool name 'get_portfolio' and description 'Full portfolio breakdown for a wallet: total USD value, all token holdings, and all DeFi app positions' indicates data retrieval with no modification.
Attacks that exploit this kind of access
Full portfolio breakdown for a wallet: total USD value, all token holdings, and all DeFi app positions across networks. Use this when the user wants a complete picture of what a wallet holds. It is categorised as a Read tool in the Zapper MCP Server, which means it retrieves data without modifying state.
Register the Zapper MCP server in PolicyLayer and add a rule for get_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 Zapper. Nothing to install.
get_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_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_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_portfolio is provided by the Zapper MCP server (mehdi-loup/zapper-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 →