AI agents call madeonsol_coordination_history 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.
The tool is purely informational, accessing historical data about coordination alerts. It performs no writes, deletions, financial transactions, or code execution. The 'ULTRA only' access restriction indicates it is a gated read operation. Severity is low because misuse by an AI agent would only expose or report past coordination data, with no side effects on system state or financial exposure.
From the tool's definition Tool retrieves 'past coordination alert fires with token, coordination score, KOL count, and timing'—all query/retrieval operations with no modification, deletion, or execution of external code.
Attacks that exploit this kind of access
Coordination history — past coordination alert fires with token, coordination score, KOL count, and timing. 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_coordination_history: 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_coordination_history 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_coordination_history 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_coordination_history. 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_coordination_history 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 →