Recent first-KOL-touch events — every time a tracked KOL was the first to buy a token mint. Filterable by scout tier (S/A/B/C from mv_kol_scout_score), KOL winrate, token age, etc. Backtest: top scouts attract ≥3 follow-on KOLs within 4h ~50% of the time vs ~14% baseline. Median lead time before ...
AI agents call madeonsol_kol_first_touches 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 is a data retrieval and query tool. It returns intelligence about KOL trading behavior (who was first to buy tokens) and allows filtering/analysis of that data. The mention of backtesting and trading signals indicates it supports decision-making based on historical data, but the tool itself performs no write operations, financial transactions, or code execution. It is purely informational.
From the tool's definition Tool retrieves 'Recent first-KOL-touch events' with filtering options (scout tier, winrate, token age, etc.).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Recent first-KOL-touch events — every time a tracked KOL was the first to buy a token mint. Filterable by scout tier (S/A/B/C from mv_kol_scout_score), KOL winrate, token age, etc. Backtest: top scouts attract ≥3 follow-on KOLs within 4h ~50% of the time vs ~14% baseline. Median lead time before second KOL is 12s — for trading this signal, use the WebSocket channel rather than polling. 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_kol_first_touches: 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_kol_first_touches 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_kol_first_touches 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_kol_first_touches. 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_kol_first_touches 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 →