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

tengu_v3_copilot_thesis_alerts

EMPTY UNTIL FIRST USE — not broken. Tracked decisions live in Redis and a row is appended ONLY on a state CHANGE, so this populates the FIRST time a tracked decision transitions. Say that to the user rather than reporting an outage. Alerts from the tracked-decision monitor: thesis intact/weakenin...

SERVERTengu SOURCEHlobo-dev/tengu-mcp
Low RISK CLASS
Category Read
Parameters 30 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v3-copilot-thesis-alerts.md

What tengu_v3_copilot_thesis_alerts does on Tengu

AI agents call tengu_v3_copilot_thesis_alerts 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.

ParameterTypeRequiredDescription
limit integer
ticker string
since_hours number

Parameters from the server's own tool schema.

Why tengu_v3_copilot_thesis_alerts is rated Low

Even though tengu_v3_copilot_thesis_alerts 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.

Risk signalsBulk/mass operation — affects multiple targets

Questions about tengu_v3_copilot_thesis_alerts

What does the tengu_v3_copilot_thesis_alerts tool do? +

EMPTY UNTIL FIRST USE — not broken. Tracked decisions live in Redis and a row is appended ONLY on a state CHANGE, so this populates the FIRST time a tracked decision transitions. Say that to the user rather than reporting an outage. Alerts from the tracked-decision monitor: thesis intact/weakening/broken transitions, earnings-imminent, interval breaches — poll after decision_track. The 2x/day monitor job sweeps every tracked decision and appends a row ONLY on state change (deduped), so every alert here is a NEW transition worth surfacing. alert_type in {status_change, earnings_imminent, interval_breach, stale_decision}; each row carries entry/last price, realised return, score_original → score_current delta, prev_status → thesis_status, severity and a render-ready narrative. Filter with ?ticker= and ?since_hours= (default 72). It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.

What parameters does tengu_v3_copilot_thesis_alerts accept? +

tengu_v3_copilot_thesis_alerts accepts 3 parameters: limit, ticker, since_hours. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_copilot_thesis_alerts? +

Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_copilot_thesis_alerts: 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_copilot_thesis_alerts? +

tengu_v3_copilot_thesis_alerts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit tengu_v3_copilot_thesis_alerts? +

Yes. Add a rate_limit block to the tengu_v3_copilot_thesis_alerts 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_copilot_thesis_alerts completely? +

Set action: deny in the PolicyLayer policy for tengu_v3_copilot_thesis_alerts. 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_copilot_thesis_alerts? +

tengu_v3_copilot_thesis_alerts 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

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