Low Risk

get_live_market

get_live_market

How to control get_live_market ↓

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

Low Risk

Despite the empty description for this specific tool, contextual analysis of the server's purpose (Nepal Stock Exchange market data access) and the consistent read-only pattern of sibling tools strongly indicates this is a data retrieval function. No side effects, modifications, or external actions are evident.

From the tool's definition Tool name 'get_live_market' indicates data retrieval. Sibling tools (get_company_floorsheet, get_company_list, get_daily_*_graph, etc.) are all read-only queries returning market data with no modification or execution capabilities.

Documented attack patterns abuse exactly the kind of access get_live_market gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Nepse API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_live_market:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_live_market": {}
  }
}

get_live_market is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Nepse API MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_live_market tool do? +

get_live_market. It is categorised as a Read tool in the Nepse API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_live_market? +

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

What risk level is get_live_market? +

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

Can I rate-limit get_live_market? +

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

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

get_live_market is provided by the Nepse API MCP Server MCP server (surajrimal07/nepseapi-unofficial). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nepse API MCP Server tool call.

Deterministic rules across all 38 Nepse API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

38 Nepse API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.