Get stocks with the highest insider trading activity (by volume). Shows which tickers have the most insider interest right now.
AI agents call get_top_movers 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 queries and retrieves aggregated market intelligence data about insider trading volumes and activity levels. It performs no modifications, executions, deletions, or financial transactions. It is purely informational—analogous to a search or list operation on a financial database.
From the tool's definition Tool name 'get_top_movers' and description 'Get stocks with the highest insider trading activity (by volume). Shows which tickers have the most insider interest right now' indicates a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Get stocks with the highest insider trading activity (by volume). Shows which tickers have the most insider interest right now. 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_top_movers: 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_top_movers 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_top_movers 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_top_movers. 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_top_movers 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 →