wallet_get_portfolio
Returns native ETH from Base RPC and indexed ERC-20 holdings from Blockscout. Token indexing can be incomplete or delayed, so verify material balances on-chain.
This record as markdown: /tools/awesome-base-mcp/wallet-get-portfolio.md
What wallet_get_portfolio does on Awesome Base
AI agents call wallet_get_portfolio to retrieve information from Awesome Base without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wallet_get_portfolio is rated Low
Tool retrieves portfolio balances without modifying state or executing transactions.
From the tool's definition Returns native ETH and ERC-20 holdings; queries data from RPC and Blockscout.
Attacks that exploit this kind of access
The rule that runs wallet_get_portfolio safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Awesome Base, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wallet_get_portfolio, this is the rule to start with:
wallet_get_portfolio is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Awesome Base, apply this rule, and every wallet_get_portfolio call is checked against it from then on.
Questions about wallet_get_portfolio
Returns native ETH from Base RPC and indexed ERC-20 holdings from Blockscout. Token indexing can be incomplete or delayed, so verify material balances on-chain. It is categorised as a Read tool in the Awesome Base MCP Server, which means it retrieves data without modifying state.
Register the Awesome Base MCP server in PolicyLayer and add a rule for wallet_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 Awesome Base. Nothing to install.
wallet_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 wallet_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 wallet_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.
wallet_get_portfolio is provided by the Awesome Base MCP server (B5-Software/awesome-base-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Awesome Base, and thousands of servers like it.
This server
Across the catalogue