Get the insider trading performance leaderboard — which insiders have the best 30/90-day returns after their trades.
AI agents call get_leaderboard to retrieve information from Lynx Mi/lynx Mi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and presents aggregated performance data from a market intelligence database. It is purely informational—it queries historical insider trade outcomes without creating, modifying, deleting, or executing any external operations. The data returned (leaderboard rankings) has no side effects on the underlying system or user accounts.
From the tool's definition Tool name 'get_leaderboard' and description 'Get the insider trading performance leaderboard' indicate a data retrieval operation that queries historical insider trading performance metrics.
Attacks that exploit this kind of access
Get the insider trading performance leaderboard — which insiders have the best 30/90-day returns after their trades. It is categorised as a Read tool in the Lynx Mi/lynx Mi MCP Server, which means it retrieves data without modifying state.
Register the Lynx Mi/lynx Mi MCP server in PolicyLayer and add a rule for get_leaderboard: 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 Lynx Mi/lynx Mi. Nothing to install.
get_leaderboard 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 get_leaderboard 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 get_leaderboard. 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.
get_leaderboard is provided by the Lynx Mi/lynx Mi MCP server (lynx-mi/lynx-mi-mcp). 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 →