tengu_copilot_score_ticker
Full per-ticker quant analysis. CALL THIS when the user asks about any specific stock (e.g. 'should I buy NVDA', 'what do you think of TSLA'). Returns blended_score, decile, conformal expected-return interval (90% band), 12-voter breakdown, factor tier, regime context, suggested position size, an...
This record as markdown: /tools/tengu-mcp/tengu-copilot-score-ticker.md
What tengu_copilot_score_ticker does on Tengu
AI agents call tengu_copilot_score_ticker 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). |
asset_class | string | — |
Parameters from the server's own tool schema.
Why tengu_copilot_score_ticker is rated Low
Even though tengu_copilot_score_ticker 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_score_ticker 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_score_ticker, this is the rule to start with:
tengu_copilot_score_ticker 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_score_ticker call is checked against it from then on.
Questions about tengu_copilot_score_ticker
Full per-ticker quant analysis. CALL THIS when the user asks about any specific stock (e.g. 'should I buy NVDA', 'what do you think of TSLA'). Returns blended_score, decile, conformal expected-return interval (90% band), 12-voter breakdown, factor tier, regime context, suggested position size, and a self-contained narrative. Use the narrative as a quotable summary; use the structured fields for follow-up questions. NAMESPACE: FIRM's universe is US EQUITIES. Nine tickers (BTC ETH LINK LTC COMP ARB NEAR APT ATOM) are ALSO crypto symbols; for those the response carries a ticker_collision block stating the score describes the US-listed EQUITY. If the user means the CRYPTO asset pass asset_class=crypto, which 404s (no FIRM crypto model yet). NEVER present an equity score as a crypto view. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.
tengu_copilot_score_ticker accepts 2 parameters: ticker, asset_class. 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_score_ticker: 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_score_ticker 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_score_ticker 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_score_ticker. 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_score_ticker 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