AI agents call madeonsol_alpha_linked 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 queries behavioral blockchain data to identify wallet relationships. It has no side effects and does not execute transactions, modify state, or delete data. However, severity is medium rather than low because the behavioral linking of wallets could enable wallet deanonymization, address clustering, or targeted monitoring of trading activity—sensitive privacy concerns in the context of crypto KOL/trading…
From the tool's definition Tool retrieves and queries data about 'wallets behaviorally linked to a target wallet'—it performs analysis and returns information without modifying, deleting, or executing actions.
Attacks that exploit this kind of access
Wallets behaviorally linked to a target wallet (co-bought 3+ tokens within 2 seconds). ULTRA only. 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_alpha_linked: 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_alpha_linked 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_alpha_linked 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_alpha_linked. 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_alpha_linked 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 →