New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

tengu_v3_intel_insider_flow

INSIDER TRANSACTIONS SPLIT BY WHETHER THE TRADE WAS PRE-SCHEDULED — Form 4/5 activity for one company with the metadata free feeds drop: the Rule 10b5-1 flag and the filing lag. Sales made under a 10b5-1 plan were scheduled in advance and carry NO view, so they are aggregated separately from disc...

SERVERTengu SOURCEHlobo-dev/tengu-mcp
Critical RISK CLASS
Category Destructive
Parameters 61 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v3-intel-insider-flow.md

What tengu_v3_intel_insider_flow does on Tengu

AI agents call tengu_v3_intel_insider_flow to permanently remove resources in Tengu, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
end string
as_of string
limit integer
start string
ticker string Yes Path parameter 'ticker' (required).
record_type string

Parameters from the server's own tool schema.

Why tengu_v3_intel_insider_flow is rated Critical

An AI agent that decides to call tengu_v3_intel_insider_flow doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Tengu is gone. There is no undo for destructive operations.

Questions about tengu_v3_intel_insider_flow

What does the tengu_v3_intel_insider_flow tool do? +

INSIDER TRANSACTIONS SPLIT BY WHETHER THE TRADE WAS PRE-SCHEDULED — Form 4/5 activity for one company with the metadata free feeds drop: the Rule 10b5-1 flag and the filing lag. Sales made under a 10b5-1 plan were scheduled in advance and carry NO view, so they are aggregated separately from discretionary trades and never blended into one 'net insider flow'; a third bucket holds rows with no plan flag, which is unknown, not discretionary. Only open-market buys and sells enter the flow buckets — grants, option exercises and tax-withholding are counted apart. Use as_of to reproduce what was PUBLIC on a date: it filters on the filing date, the only correct as-of key for insider data (a trade-date filter leaks late-filed trades). It is categorised as a Destructive tool in the Tengu MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does tengu_v3_intel_insider_flow accept? +

tengu_v3_intel_insider_flow accepts 6 parameters: end, as_of, limit, start, ticker, record_type. Required: ticker. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_intel_insider_flow? +

Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_intel_insider_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 Tengu. Nothing to install.

What risk level is tengu_v3_intel_insider_flow? +

tengu_v3_intel_insider_flow is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit tengu_v3_intel_insider_flow? +

Yes. Add a rate_limit block to the tengu_v3_intel_insider_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.

How do I block tengu_v3_intel_insider_flow completely? +

Set action: deny in the PolicyLayer policy for tengu_v3_intel_insider_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.

What MCP server provides tengu_v3_intel_insider_flow? +

tengu_v3_intel_insider_flow 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tengu's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.