scan_token
AI agents call scan_token to retrieve information from VerdictSwarm MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a security scan/audit of a token, which is fundamentally a read operation that retrieves or analyzes data about the token's risk profile. While the description is empty (reducing confidence slightly), the server's stated purpose of providing 'real-time security audits and risk scoring' and the presence of similar sibling tools like 'get_token_report' and 'check_rug_risk' indicate this is an…
From the tool's definition Tool name 'scan_token' with context from sibling tools (check_rug_risk, get_quick_score, get_token_report, verify_payment) and server description indicating 'security audits and risk scoring' suggests data retrieval and analysis without modification.
Attacks that exploit this kind of access
scan_token. It is categorised as a Read tool in the VerdictSwarm MCP Server MCP Server, which means it retrieves data without modifying state.
Register the VerdictSwarm MCP Server MCP server in PolicyLayer and add a rule for scan_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 VerdictSwarm MCP Server. Nothing to install.
scan_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 scan_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 scan_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.
scan_token is provided by the VerdictSwarm MCP Server MCP server (sentien-labs/verdictswarm-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 →