Monitor new pump.fun token launches for a specified duration. Returns all launches seen during that window.
AI agents call watch_pump_launches to retrieve information from Agenti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Documented attack patterns abuse exactly the kind of access watch_pump_launches gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agenti, and nothing reaches the server without passing your rules. This is the rule we recommend for watch_pump_launches:
{
"version": "1",
"default": "deny",
"tools": {
"watch_pump_launches": {}
}
}watch_pump_launches is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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.
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.
watch_pump_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 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.
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.
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.
Deterministic rules across all 73 Agenti tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
73 Agenti tools catalogued and risk-classified — across an index of 42,500+ MCP servers.