tengu_v3_intel_macro_snapshot
NOW WITH a credit block: CDX IG/HY on-the-run 5Y composite spreads + 1-session delta (T-2 by source, cadence-aware staleness; full series at /api/v3/credit/indices). Cross-asset macro composite returning REAL underlying values, all real-time where the data source permits. Fields: vix (real-time s...
This record as markdown: /tools/tengu-mcp/tengu-v3-intel-macro-snapshot.md
What tengu_v3_intel_macro_snapshot does on Tengu
AI agents call tengu_v3_intel_macro_snapshot 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 |
|---|---|---|---|
freshness | string | — |
Parameters from the server's own tool schema.
Why tengu_v3_intel_macro_snapshot is rated Low
Even though tengu_v3_intel_macro_snapshot 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
Attacks that exploit this kind of access
The rule that runs tengu_v3_intel_macro_snapshot 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_macro_snapshot, this is the rule to start with:
tengu_v3_intel_macro_snapshot 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_v3_intel_macro_snapshot call is checked against it from then on.
Questions about tengu_v3_intel_macro_snapshot
NOW WITH a credit block: CDX IG/HY on-the-run 5Y composite spreads + 1-session delta (T-2 by source, cadence-aware staleness; full series at /api/v3/credit/indices). Cross-asset macro composite returning REAL underlying values, all real-time where the data source permits. Fields: vix (real-time spot), ten_year_yield_pct (FRED DGS10, %), usd_index_narrow_dxy (computed from FRED 6-pair basket via the standard geometric weighted formula — the institutional standard ~99), usd_index_trade_weighted_broad (FRED DTWEXBGS — Fed's broader policy measure ~118), wti_oil_usd_bbl (FRED DCOILWTICO, $/bbl), gold_usd_oz (real-time forex spot, $/oz), sp500 (real-time index; SPY×10 emergency fallback), nasdaq100 (real-time index; QQQ×41 emergency fallback), djia (real-time index; null when unavailable — no ETF proxy emitted), russell2000 (real-time index; IWM×10 emergency fallback). Every numeric field is gated by a plausibility guard — out-of-band values are nulled with an error.implausible_value field rather than served, so the chat Brain never cites a wrong number with the [macro_snapshot] tag. Includes vol_regime (low_vol/normal/elevated/stress per VIX bucket), data_freshness timestamp, and a sources block with the series reference for each indicator. 60s cache. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.
tengu_v3_intel_macro_snapshot accepts 1 parameter: freshness. 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_v3_intel_macro_snapshot: 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_v3_intel_macro_snapshot 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_v3_intel_macro_snapshot 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_v3_intel_macro_snapshot. 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_v3_intel_macro_snapshot 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