Scan newly launched tokens — filters for legitimate new launches vs. honeypots. Returns risk score, liquidity, deployer history, and launch metadata.
AI agents call token_launches 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.
This tool queries and analyzes metadata about cryptocurrency token launches to identify risks and legitimacy. While the data it accesses concerns financial instruments (crypto tokens), the tool itself performs read-only reconnaissance—it scans, filters, and returns analysis without executing trades, moving funds, or modifying blockchain state.
From the tool's definition Tool name 'token_launches' combined with description 'Scan newly launched tokens' and 'Returns risk score, liquidity, deployer history, and launch metadata' indicates data retrieval and analysis only.
Attacks that exploit this kind of access
Scan newly launched tokens — filters for legitimate new launches vs. honeypots. Returns risk score, liquidity, deployer history, and launch metadata. It is categorised as a Read tool in the Mcp Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Server MCP server in PolicyLayer and add a rule for token_launches: 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.
token_launches 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 token_launches 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 token_launches. 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.
token_launches 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 →