Aggregate insider money flow by sector. Shows which sectors are seeing the most insider buying vs. selling — a leading indicator of sector rotation.
AI agents call get_sector_flow 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 performs data retrieval and aggregation of market intelligence (SEC insider trades and related metrics). It queries existing public market data to show sector-level flow patterns but does not create, modify, delete, or execute any actions. The tool is read-only analysis with no side effects beyond returning information to the user.
From the tool's definition Tool description states 'Aggregate insider money flow by sector' and 'Shows which sectors are seeing the most insider buying vs. selling' — these are purely informational aggregations and displays of public market data.
Attacks that exploit this kind of access
Aggregate insider money flow by sector. Shows which sectors are seeing the most insider buying vs. selling — a leading indicator of sector rotation. 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_sector_flow: 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_sector_flow 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_sector_flow 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_sector_flow. 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_sector_flow 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 →