tengu_copilot_ticker_full
OMNIBUS aggregation for one ticker — Brain's primary single-stock verdict path. Pulls BOTH the 5-layer transparency cluster AND the 7-layer smartmoney cluster in ONE call (up to 12 underlying tools in parallel inside FIRM). Replaces Brain's 24-72 HTTP-burst fan-out with a single call. Use for 'sh...
This record as markdown: /tools/tengu-mcp/tengu-copilot-ticker-full.md
What tengu_copilot_ticker_full does on Tengu
AI agents call tengu_copilot_ticker_full 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 | Yes | Path parameter 'ticker' (required). |
cache_max_age_s | number | — | |
include_smartmoney | boolean | — | |
candidate_weight_pct | number | — | |
include_transparency | boolean | — |
Parameters from the server's own tool schema.
Why tengu_copilot_ticker_full is rated Low
Even though tengu_copilot_ticker_full 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_copilot_ticker_full 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_copilot_ticker_full, this is the rule to start with:
tengu_copilot_ticker_full 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_copilot_ticker_full call is checked against it from then on.
Questions about tengu_copilot_ticker_full
OMNIBUS aggregation for one ticker — Brain's primary single-stock verdict path. Pulls BOTH the 5-layer transparency cluster AND the 7-layer smartmoney cluster in ONE call (up to 12 underlying tools in parallel inside FIRM). Replaces Brain's 24-72 HTTP-burst fan-out with a single call. Use for 'should I buy X?' / 'what do you think of Y?' / 'verdict on Z' shapes. include_smartmoney and include_transparency flags let comparison views skip clusters they don't need. Cache TTL 60s. Pass cache_max_age_s=0 to bypass cache. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.
tengu_copilot_ticker_full accepts 5 parameters: ticker, cache_max_age_s, include_smartmoney, candidate_weight_pct, include_transparency. 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_copilot_ticker_full: 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_copilot_ticker_full 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_copilot_ticker_full 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_copilot_ticker_full. 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_copilot_ticker_full 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