Low Risk

get_price_volume

get_price_volume

How to control get_price_volume ↓

AI agents call get_price_volume 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

Based on naming convention and sibling tools on the Nepse API server, this tool retrieves market data (price and volume information) without modifying, deleting, or executing arbitrary operations. It is a data retrieval operation with no side effects, placing it in the Read category.

From the tool's definition Tool name 'get_price_volume' with 'get_' prefix and sibling tools like 'get_company_list', 'get_daily_bank_subindex_graph' all indicate retrieval operations. No description provided, but the pattern is clear.

Documented attack patterns abuse exactly the kind of access get_price_volume 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_price_volume:

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

get_price_volume 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_price_volume tool do? +

get_price_volume. 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_price_volume? +

Register the Nepse API MCP Server MCP server in PolicyLayer and add a rule for get_price_volume: 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_price_volume? +

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

Can I rate-limit get_price_volume? +

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

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

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