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

tengu_v3_reference_batch

BATCH CROSSWALK — up to 100 symbols resolved in ONE pass, each returning its current identifiers (CUSIP9, CUSIP8, ISIN, SEDOL, ticker, estimate-vendor ticker), its issuer keys (gvkey, CUSIP6, regulator filer number), which rung matched and its status. This is the endpoint for mapping a whole port...

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-reference-batch.md

What tengu_v3_reference_batch does on Tengu

AI agents call tengu_v3_reference_batch 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
symbols string Yes
prefer_country string

Parameters from the server's own tool schema.

Why tengu_v3_reference_batch is rated Low

Even though tengu_v3_reference_batch 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.

Questions about tengu_v3_reference_batch

What does the tengu_v3_reference_batch tool do? +

BATCH CROSSWALK — up to 100 symbols resolved in ONE pass, each returning its current identifiers (CUSIP9, CUSIP8, ISIN, SEDOL, ticker, estimate-vendor ticker), its issuer keys (gvkey, CUSIP6, regulator filer number), which rung matched and its status. This is the endpoint for mapping a whole portfolio or watchlist in a single call rather than N of them. Every symbol comes back with an explicit status — resolved, historical (renamed or delisted; the security and what it trades as now are both returned), ambiguous (shared by more than one current security: the candidates are listed and NO identity is guessed) or unknown (not carried). Symbols beyond the 100 limit come back as explicit over_limit entries, never silently dropped, and the response reports how many of the requested symbols resolved as a number and a percentage (measured 2026-08-02 on a 102-symbol large-cap list: 100 looked up, 99 resolved, 1 historical, 2 over_limit). 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_reference_batch accept? +

tengu_v3_reference_batch accepts 2 parameters: symbols, prefer_country. Required: symbols. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_reference_batch? +

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

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

Can I rate-limit tengu_v3_reference_batch? +

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

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

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