AI agents call get_supply_demand 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 follows the 'get_' prefix pattern of all sibling tools on this Nepal Stock Exchange data API server, indicating a data retrieval operation with no side effects. The lack of description lowers confidence slightly, but the context strongly suggests this retrieves supply/demand market data rather than modifying or deleting it.
From the tool's definition Tool name 'get_supply_demand' implies data retrieval; consistent with sibling tools (get_company_floorsheet, get_company_list, get_daily_*_subindex_graph) which are all read-only queries of market data.
Documented attack patterns abuse exactly the kind of access get_supply_demand 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_supply_demand:
{
"version": "1",
"default": "deny",
"tools": {
"get_supply_demand": {}
}
}get_supply_demand 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_supply_demand. 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_supply_demand: 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_supply_demand 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_supply_demand 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_supply_demand. 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_supply_demand 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.