Check whether a Solana wallet address is a known KOL or smart money wallet. Returns rank, PnL, and source.
AI agents call check_smart_wallet to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns information about wallet addresses (rank, PnL, source) with no side effects. It does not create, modify, delete, or execute any financial transactions. The classification aligns with 'Read' category—it retrieves or queries data with no side effects.
From the tool's definition The tool 'Check whether a Solana wallet address is a known KOL or smart money wallet. Returns rank, PnL, and source' performs a query/lookup operation that retrieves wallet metadata without modifying any data or executing transactions.
Documented attack patterns abuse exactly the kind of access check_smart_wallet gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for check_smart_wallet:
{
"version": "1",
"default": "deny",
"tools": {
"check_smart_wallet": {}
}
}check_smart_wallet 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.
Check whether a Solana wallet address is a known KOL or smart money wallet. Returns rank, PnL, and source. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti MCP server in PolicyLayer and add a rule for check_smart_wallet: 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 Agenti. Nothing to install.
check_smart_wallet 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 check_smart_wallet 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 check_smart_wallet. 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.
check_smart_wallet is provided by the Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.