Cross-asset portfolio risk analyzer. Pass a wallet address — auto-fetches all Base on-chain holdings (ERC-20 + ETH), values each position, flags stablecoin % and top concentration. Also accepts stock tickers and token contracts. Returns unified risk score 1-10, AI narrative, and cross_asset_flags.
AI agents call wealth_pulse to retrieve information from Mcp Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet | string | — | |
tickers | string | — | |
contracts | string | — |
Parameters from the server's own tool schema.
wealth_pulse is fundamentally a data retrieval and analysis tool. It reads wallet holdings, fetches market values, and performs risk calculations. While it accesses sensitive financial portfolio information (which justifies medium severity due to privacy exposure and potential targeting risk if wallet address is leaked), it performs no write, execute, or destructive operations.
From the tool's definition Tool 'auto-fetches all Base on-chain holdings', 'values each position', 'flags stablecoin %', and 'returns unified risk score, AI narrative, and cross_asset_flags' — all retrieval and analysis operations with no modification or execution of transactions.
Attacks that exploit this kind of access
Cross-asset portfolio risk analyzer. Pass a wallet address — auto-fetches all Base on-chain holdings (ERC-20 + ETH), values each position, flags stablecoin % and top concentration. Also accepts stock tickers and token contracts. Returns unified risk score 1-10, AI narrative, and cross_asset_flags. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
wealth_pulse accepts 3 parameters: wallet, tickers, contracts. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Server MCP server in PolicyLayer and add a rule for wealth_pulse: 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 Mcp Server. Nothing to install.
wealth_pulse 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 wealth_pulse 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 wealth_pulse. 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.
wealth_pulse is provided by the Mcp Server MCP server (Homie4570/lso-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 →