AI agents call get_price_history 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.
The tool name and server context clearly indicate this retrieves historical price data from the Nepal Stock Exchange. No write, delete, execute, or financial transaction capabilities are present. Tool description is empty, but the naming pattern and context of read-only market data access tools on the same server provide strong evidence this is a simple data retrieval function with no side effects.
From the tool's definition Tool name 'get_price_history' indicates data retrieval. Server description states it provides 'structured access to Nepal Stock Exchange market data' for 'querying real-time stock data and market analysis'.
Documented attack patterns abuse exactly the kind of access get_price_history 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_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_price_history": {}
}
}get_price_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_price_history. It is categorised as a Read tool in the Nepse API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nepse API MCP Server MCP server in PolicyLayer and add a rule for get_price_history: 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.
get_price_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_price_history 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.
Set action: deny in the PolicyLayer policy for get_price_history. 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.
get_price_history 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.
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.