AI agents call get_wallet_activity to retrieve information from Wallet Inspector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve wallet activity information without modifying state or performing financial transactions. The prefix 'get_' and sibling tools naming convention ('get_wallet_balance', 'get_wallet_transactions') strongly suggest read-only access. It belongs in the Read category.
From the tool's definition Tool name 'get_wallet_activity' and sibling tools 'get_wallet_balance' and 'get_wallet_transactions' all suggest read-only retrieval of financial data. The 'get_' prefix and context of a wallet inspector server indicate query operations without modification.
Documented attack patterns abuse exactly the kind of access get_wallet_activity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wallet Inspector, and nothing reaches the server without passing your rules. This is the rule we recommend for get_wallet_activity:
{
"version": "1",
"default": "deny",
"tools": {
"get_wallet_activity": {}
}
}get_wallet_activity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_wallet_activity. It is categorised as a Read tool in the Wallet Inspector MCP Server, which means it retrieves data without modifying state.
Register the Wallet Inspector MCP server in PolicyLayer and add a rule for get_wallet_activity: 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 Wallet Inspector. Nothing to install.
get_wallet_activity 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_activity 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_activity. 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_activity is provided by the Wallet Inspector MCP server (kukapay/wallet-inspector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wallet Inspector, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Wallet Inspector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.