tengu_v3_tape_microstructure
60s microstructure windows per ticker from FIRM's live tape: rolling vwap, trade count/avg size, block count/vol, buy/sell imbalance, large-trade premium. Call it to separate smart-money accumulation from retail moves. Active-set coverage (~few hundred names/session; empty = uncaptured); omit dat...
This record as markdown: /tools/tengu-mcp/tengu-v3-tape-microstructure.md
What tengu_v3_tape_microstructure does on Tengu
AI agents use tengu_v3_tape_microstructure to create or update resources in Tengu, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tengu environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | — | |
limit | integer | — | |
ticker | string | Yes | Path parameter 'ticker' (required). |
Parameters from the server's own tool schema.
Why tengu_v3_tape_microstructure is rated Medium
An AI agent can call tengu_v3_tape_microstructure faster than any human can review: one bad instruction and it creates or modifies resources in Tengu by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs tengu_v3_tape_microstructure 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_tape_microstructure, this is the rule to start with:
tengu_v3_tape_microstructure stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_tape_microstructure call is checked against it from then on.
Questions about tengu_v3_tape_microstructure
60s microstructure windows per ticker from FIRM's live tape: rolling vwap, trade count/avg size, block count/vol, buy/sell imbalance, large-trade premium. Call it to separate smart-money accumulation from retail moves. Active-set coverage (~few hundred names/session; empty = uncaptured); omit date for latest, capture from 2026-05-13. It is categorised as a Write tool in the Tengu MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tengu_v3_tape_microstructure accepts 3 parameters: date, limit, ticker. Required: 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_tape_microstructure: 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_tape_microstructure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tengu_v3_tape_microstructure 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_tape_microstructure. 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_tape_microstructure 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