find_index_details

Search Nubra's public index master first, then compare the closest index rows against the exchange instrument master.

Server Nubra MCP Server socials-zanskar/nubra-mcp-server
Category Read
Risk class Low
Parameters 00 required

What find_index_details does on Nubra MCP Server

AI agents call find_index_details to retrieve information from Nubra MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why find_index_details needs a policy

This tool retrieves index metadata and performs comparison operations against master data sources. There are no side effects, no data modification, no code execution, and no financial transactions. It is a read-only lookup utility typical of a data inquiry service. The low severity reflects minimal blast radius if misused — an agent could only retrieve or list index information.

From the tool's definition Tool description states 'Search Nubra's public index master' and 'compare the closest index rows' — these are query/lookup operations with no mention of modification, deletion, or execution of commands.

Questions about find_index_details

What does the find_index_details tool do? +

Search Nubra's public index master first, then compare the closest index rows against the exchange instrument master. It is categorised as a Read tool in the Nubra MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_index_details? +

Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for find_index_details: 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 Nubra MCP Server. Nothing to install.

What risk level is find_index_details? +

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

Can I rate-limit find_index_details? +

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

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

find_index_details is provided by the Nubra MCP Server MCP server (socials-zanskar/nubra-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.