madeonsol_sniper_recent

Deshred pre-confirm pump.fun deploy feed — new launches surface ~500ms before they confirm on-chain (reconstructed from shred-level data). PRO sees elite/good deployers; ULTRA sees every tier. Requires a Pro/Ultra msk_ API key.

Server Madeonsol mcp-server-madeonsol
Category Read
Risk class Low
Parameters 00 required

What madeonsol_sniper_recent does on Madeonsol

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

Why madeonsol_sniper_recent needs a policy

This tool retrieves and surfaces real-time feed data about new token launches on pump.fun using shred-level reconstruction. It is fundamentally a read/query operation — it fetches intelligence data with no side effects.

From the tool's definition Deshred pre-confirm pump.fun deploy feed — new launches surface ~500ms before they confirm on-chain (reconstructed from shred-level data)

Risk signalsBulk/mass operation — affects multiple targets

Questions about madeonsol_sniper_recent

What does the madeonsol_sniper_recent tool do? +

Deshred pre-confirm pump.fun deploy feed — new launches surface ~500ms before they confirm on-chain (reconstructed from shred-level data). PRO sees elite/good deployers; ULTRA sees every tier. Requires a Pro/Ultra msk_ API key. It is categorised as a Read tool in the Madeonsol MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on madeonsol_sniper_recent? +

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

What risk level is madeonsol_sniper_recent? +

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

Can I rate-limit madeonsol_sniper_recent? +

Yes. Add a rate_limit block to the madeonsol_sniper_recent 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 madeonsol_sniper_recent completely? +

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

madeonsol_sniper_recent is provided by the Madeonsol MCP server (mcp-server-madeonsol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.