get_instrument_details

Use this when a user asks for ref_id, tick size, lot size, nubra name, or NSE instrument details for a stock, future, or option.

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

What get_instrument_details does on Nubra MCP Server

AI agents call get_instrument_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 get_instrument_details needs a policy

This tool retrieves static instrument metadata (reference IDs, tick sizes, lot sizes, names, and exchange details). It performs a lookup query with no side effects, no code execution, no data modification, and no financial impact. The tool is purely informational and supports informed decision-making rather than triggering any action.

From the tool's definition Tool description explicitly states 'Use this when a user asks for ref_id, tick size, lot size, nubra name, or NSE instrument details' — all read-only lookups that retrieve reference data without modification or execution of trades.

Questions about get_instrument_details

What does the get_instrument_details tool do? +

Use this when a user asks for ref_id, tick size, lot size, nubra name, or NSE instrument details for a stock, future, or option. 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 get_instrument_details? +

Register the Nubra MCP Server MCP server in PolicyLayer and add a rule for get_instrument_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 get_instrument_details? +

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

Can I rate-limit get_instrument_details? +

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

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

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