tengu_v3_intel_gex

Aggregate gamma exposure (GEX) and delta exposure for one ticker from the options-flow feed. Call this when the user asks about dealer positioning or gamma levels, or whether options exposure could dampen or amplify moves in a name; pair with tengu_v3_intel_max_pain for expiry pin levels.

SERVERTengu SOURCEHlobo-dev/tengu-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v3-intel-gex.md

WHAT IT DOES

What tengu_v3_intel_gex does on Tengu

AI agents call tengu_v3_intel_gex 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).
`freshness`	string	—

Parameters from the server's own tool schema.

RISK

Why tengu_v3_intel_gex is rated Low

Even though tengu_v3_intel_gex 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_intel_gex 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_intel_gex, this is the rule to start with:

tengu_v3_intel_gex Allowed

tengu_v3_intel_gex 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_intel_gex": {}
  }
}

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

FAQ

Questions about tengu_v3_intel_gex

What does the tengu_v3_intel_gex tool do? +

What parameters does tengu_v3_intel_gex accept? +

tengu_v3_intel_gex accepts 2 parameters: ticker, freshness. Required: ticker. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_intel_gex? +

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

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

Can I rate-limit tengu_v3_intel_gex? +

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

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

tengu_v3_intel_gex 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 →