tengu_v2_crash_scenarios

SERVERTengu SOURCEHlobo-dev/tengu-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v2-crash-scenarios.md

WHAT IT DOES

What tengu_v2_crash_scenarios does on Tengu

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

RISK

Why tengu_v2_crash_scenarios is rated Low

Even though tengu_v2_crash_scenarios 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

RECOMMENDED RULE

The rule that runs tengu_v2_crash_scenarios 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_v2_crash_scenarios, this is the rule to start with:

tengu_v2_crash_scenarios Allowed

tengu_v2_crash_scenarios is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tengu_v2_crash_scenarios": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tengu, apply this rule, and every tengu_v2_crash_scenarios call is checked against it from then on.

FAQ

Questions about tengu_v2_crash_scenarios

What does the tengu_v2_crash_scenarios tool do? +

Historical crash replay through past market crash episodes. Call it when the user asks 'how would this have held up in previous crashes?' or wants tail risk anchored to real historical events; use tengu_v2_stress for hypothetical scenarios. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tengu_v2_crash_scenarios? +

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

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

Can I rate-limit tengu_v2_crash_scenarios? +

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

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

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

KEEP EXPLORING

More on Tengu, and thousands of servers like it.

This server

All 337 Tengu tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →