Check the risk profile of a Solana token by mint address.
AI agents call check_token to retrieve information from SolSentry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes threat intelligence data about Solana tokens to detect rug pulls and malicious activity. It has no side effects, does not execute code, does not modify data, and does not move funds. The worst misuse would be providing false information about a token's legitimacy, but the tool itself only reads/analyzes existing blockchain data.
From the tool's definition Tool performs token risk profile checking by mint address with no modification or deletion capabilities. Description uses 'check' and 'risk profile' language indicating query/analysis rather than state-changing operations.
Attacks that exploit this kind of access
Check the risk profile of a Solana token by mint address. It is categorised as a Read tool in the SolSentry MCP MCP Server, which means it retrieves data without modifying state.
Register the SolSentry MCP server in PolicyLayer and add a rule for check_token: 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 SolSentry MCP. Nothing to install.
check_token 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_token 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_token. 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_token is provided by the SolSentry MCP server (solsentry/solsentry-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
check_token is one line of SolSentry's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →