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

tengu_v3_fundamentals_pit_vintages

THE RESTATEMENT TRAIL for one fiscal quarter — every published version of the period in order, each with the day it became the live view, the day it was superseded, and exactly WHICH line items changed from the previous version. Call it to check whether a figure you are relying on has been quietl...

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

This record as markdown: /tools/tengu-mcp/tengu-v3-fundamentals-pit-vintages.md

What tengu_v3_fundamentals_pit_vintages does on Tengu

AI agents call tengu_v3_fundamentals_pit_vintages 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
consol string
indfmt string
popsrc string
ticker string Yes Path parameter 'ticker' (required).
datafmt string
datadate string

Parameters from the server's own tool schema.

Why tengu_v3_fundamentals_pit_vintages is rated Low

Even though tengu_v3_fundamentals_pit_vintages 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_fundamentals_pit_vintages

What does the tengu_v3_fundamentals_pit_vintages tool do? +

THE RESTATEMENT TRAIL for one fiscal quarter — every published version of the period in order, each with the day it became the live view, the day it was superseded, and exactly WHICH line items changed from the previous version. Call it to check whether a figure you are relying on has been quietly revised, and by how much: a quarter can be restated several times, and only the trail shows it. The still-current version reports a null supersede date rather than a far-future sentinel. Omit datadate for the most recent quarter held. 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_fundamentals_pit_vintages accept? +

tengu_v3_fundamentals_pit_vintages accepts 6 parameters: consol, indfmt, popsrc, ticker, datafmt, datadate. 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_fundamentals_pit_vintages? +

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

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

Can I rate-limit tengu_v3_fundamentals_pit_vintages? +

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

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

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