tengu_v3_intel_sec13f_changes
Quarter-over-quarter 13F position deltas (alternative-data), sign preserved: positive = added, negative = trimmed. Call this when the user asks 'are institutions adding or dumping X?'; set min_pct (absolute change fraction, e.g. 0.5 = 50%) to drop noise.
This record as markdown: /tools/tengu-mcp/tengu-v3-intel-sec13f-changes.md
What tengu_v3_intel_sec13f_changes does on Tengu
AI agents call tengu_v3_intel_sec13f_changes 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
fund | string | — | |
limit | integer | — | |
ticker | string | — | |
min_pct | number | — |
Parameters from the server's own tool schema.
Why tengu_v3_intel_sec13f_changes is rated Critical
An AI agent that decides to call tengu_v3_intel_sec13f_changes 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.
Attacks that exploit this kind of access
The rule that runs tengu_v3_intel_sec13f_changes 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_sec13f_changes, this is the rule to start with:
tengu_v3_intel_sec13f_changes is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Tengu, apply this rule, and every tengu_v3_intel_sec13f_changes call is checked against it from then on.
Questions about tengu_v3_intel_sec13f_changes
Quarter-over-quarter 13F position deltas (alternative-data), sign preserved: positive = added, negative = trimmed. Call this when the user asks 'are institutions adding or dumping X?'; set min_pct (absolute change fraction, e.g. 0.5 = 50%) to drop noise. 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.
tengu_v3_intel_sec13f_changes accepts 4 parameters: fund, limit, ticker, min_pct. 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_sec13f_changes: 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_sec13f_changes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the tengu_v3_intel_sec13f_changes 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_sec13f_changes. 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_sec13f_changes 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.
Across the catalogue