get_base_launches
Ranked feed of freshly-launched Base tokens, each scored for safety + momentum into one
This record as markdown: /tools/0xcnr0-rugsense/get-base-launches.md
What get_base_launches does on RugSense
AI agents call get_base_launches to retrieve information from RugSense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_base_launches is rated Low
This tool retrieves and ranks structured data about blockchain token launches. It queries an existing database or feed, applies scoring logic server-side, and returns read-only results to the caller. The agent receives information to inform decisions but cannot modify data, execute arbitrary code, delete records, or move funds through this tool alone.
From the tool's definition Tool name 'get_base_launches' and description 'Ranked feed of freshly-launched Base tokens, each scored for safety + momentum' indicate a retrieval/query operation that returns pre-computed launch data and scores.
Attacks that exploit this kind of access
The rule that runs get_base_launches safely
PolicyLayer is an MCP gateway: it sits between your AI agents and RugSense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_base_launches, this is the rule to start with:
get_base_launches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect RugSense, apply this rule, and every get_base_launches call is checked against it from then on.
Questions about get_base_launches
Ranked feed of freshly-launched Base tokens, each scored for safety + momentum into one. It is categorised as a Read tool in the RugSense MCP Server, which means it retrieves data without modifying state.
Register the RugSense MCP server in PolicyLayer and add a rule for get_base_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 RugSense. Nothing to install.
get_base_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 get_base_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 get_base_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.
get_base_launches is provided by the RugSense MCP server (0xcnr0/rugsense). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on RugSense, and thousands of servers like it.
This server
Across the catalogue