AI agents call madeonsol_almost_bonded 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.
This tool retrieves and displays ranked token data from pump.fun without creating, modifying, or deleting records. However, the context of a KOL intelligence API combined with financial market data (pump.fun tokens, ranking by velocity) elevates severity from low to medium—the data could influence crypto trading decisions.
From the tool's definition Tool queries and ranks pre-bond pump.fun tokens by velocity metrics. Name contains 'almost' and description uses language like 'Pre-bond', 'approaching', 'ranked by VELOCITY' indicating data retrieval and ranking without modification or deletion.
Attacks that exploit this kind of access
Pre-bond pump.fun tokens approaching graduation, ranked by VELOCITY (Δprogress/min) —. It is categorised as a Read tool in the Madeonsol MCP Server, which means it retrieves data without modifying state.
Register the Madeonsol MCP server in PolicyLayer and add a rule for madeonsol_almost_bonded: 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.
madeonsol_almost_bonded 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 madeonsol_almost_bonded 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 madeonsol_almost_bonded. 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.
madeonsol_almost_bonded 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.
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 →