AI agents call get_nh_index to retrieve information from Tushare MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on naming convention and context of sibling tools that retrieve financial data without modification, this appears to be a data retrieval function querying index information. The empty description lowers confidence slightly, but the 'get_' prefix and server purpose (query and search stock information) strongly indicate a Read operation with minimal risk.
From the tool's definition Tool name 'get_nh_index' suggests retrieval of index data. Sibling tools like 'get_block_trade', 'get_concept_moneyflow_dc', and 'get_cache_stats' are all read-only queries. No parameters described, and empty tool description provides limited specificity.
Documented attack patterns abuse exactly the kind of access get_nh_index gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tushare MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nh_index:
{
"version": "1",
"default": "deny",
"tools": {
"get_nh_index": {}
}
}get_nh_index 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_nh_index. It is categorised as a Read tool in the Tushare MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tushare MCP Server MCP server in PolicyLayer and add a rule for get_nh_index: 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 Tushare MCP Server. Nothing to install.
get_nh_index 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_nh_index 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_nh_index. 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_nh_index is provided by the Tushare MCP Server MCP server (zhewenzhang/tushare_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 66 Tushare MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
66 Tushare MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.