tengu_v3_intel_insider_flow_coverage
What insider history exists, for which dates, and how much of it carries a Rule 10b5-1 plan flag — rows by record type, distinct filers, the transaction- and filing-date spans, and the share of rows that actually carry the plan flag. Call it before reading a plan split as complete: rows without t...
This record as markdown: /tools/tengu-mcp/tengu-v3-intel-insider-flow-coverage.md
What tengu_v3_intel_insider_flow_coverage does on Tengu
AI agents call tengu_v3_intel_insider_flow_coverage to retrieve information from Tengu without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
ticker | string | — |
Parameters from the server's own tool schema.
Why tengu_v3_intel_insider_flow_coverage is rated Low
Even though tengu_v3_intel_insider_flow_coverage only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs tengu_v3_intel_insider_flow_coverage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tengu, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tengu_v3_intel_insider_flow_coverage, this is the rule to start with:
tengu_v3_intel_insider_flow_coverage is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tengu, apply this rule, and every tengu_v3_intel_insider_flow_coverage call is checked against it from then on.
Questions about tengu_v3_intel_insider_flow_coverage
What insider history exists, for which dates, and how much of it carries a Rule 10b5-1 plan flag — rows by record type, distinct filers, the transaction- and filing-date spans, and the share of rows that actually carry the plan flag. Call it before reading a plan split as complete: rows without the flag are unknown, and this says how many there are. Pass a ticker for per-company coverage. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.
tengu_v3_intel_insider_flow_coverage accepts 1 parameter: ticker. The full parameter table on this page comes from the server's own tool schema.
Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_intel_insider_flow_coverage: 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 Tengu. Nothing to install.
tengu_v3_intel_insider_flow_coverage 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 tengu_v3_intel_insider_flow_coverage 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 tengu_v3_intel_insider_flow_coverage. 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.
tengu_v3_intel_insider_flow_coverage is provided by the Tengu MCP server (Hlobo-dev/tengu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tengu, and thousands of servers like it.
This server
Across the catalogue