watch_pump_launches

Monitor new pump.fun token launches for a specified duration. Returns all launches seen during that window.

SERVERAgenti SOURCEnirholas/agenti

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/nirholas-agenti/watch-pump-launches.md

WHAT IT DOES

What watch_pump_launches does on Agenti

AI agents call watch_pump_launches to retrieve information from Agenti without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why watch_pump_launches is rated Low

Despite the server's financial context (cryptocurrency operations), this specific tool only monitors and retrieves data about token launches. It does not execute trades, transfer assets, modify state, or create financial obligations. The monitoring/watching pattern indicates passive observation rather than active financial transactions.

From the tool's definition Tool description states 'Monitor new pump.fun token launches' and 'Returns all launches seen during that window' - these are retrieval/query operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs watch_pump_launches safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For watch_pump_launches, this is the rule to start with:

watch_pump_launches Allowed

watch_pump_launches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "watch_pump_launches": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every watch_pump_launches call is checked against it from then on.

FAQ

Questions about watch_pump_launches

What does the watch_pump_launches tool do? +

Monitor new pump.fun token launches for a specified duration. Returns all launches seen during that window. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on watch_pump_launches? +

Register the Agenti MCP server in PolicyLayer and add a rule for watch_pump_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 Agenti. Nothing to install.

What risk level is watch_pump_launches? +

watch_pump_launches is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit watch_pump_launches? +

Yes. Add a rate_limit block to the watch_pump_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.

How do I block watch_pump_launches completely? +

Set action: deny in the PolicyLayer policy for watch_pump_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.

What MCP server provides watch_pump_launches? +

watch_pump_launches 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.

KEEP EXPLORING

More on Agenti, and thousands of servers like it.

This server

All 73 Agenti tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →