tengu_v3_stream_status

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-v3-stream-status.md

WHAT IT DOES

What tengu_v3_stream_status does on Tengu

AI agents call tengu_v3_stream_status 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_v3_stream_status is rated Low

Even though tengu_v3_stream_status 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_v3_stream_status 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_stream_status, this is the rule to start with:

tengu_v3_stream_status Allowed

tengu_v3_stream_status 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_v3_stream_status": {}
  }
}

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_v3_stream_status call is checked against it from then on.

FAQ

Questions about tengu_v3_stream_status

What does the tengu_v3_stream_status tool do? +

Bounded Redis reachability plus expiring market-producer and signal-pipeline heartbeats, per-capability readiness, coverage modes/limits and known SSE endpoints. Call before claiming live data or diagnosing missing/stale feeds. 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_v3_stream_status? +

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

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

Can I rate-limit tengu_v3_stream_status? +

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

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

tengu_v3_stream_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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