Low Risk

get_lhb_detail

get_lhb_detail

How to control get_lhb_detail ↓

What get_lhb_detail does on A Share

AI agents call get_lhb_detail to retrieve information from A Share without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_lhb_detail needs a policy

This tool is classified as Read because: (1) the server's explicit purpose is 'data query' (数据查询); (2) all sibling tools are query functions retrieving financial/market data; (3) the 'get_lhb_detail' naming convention (LHB likely refers to '龙虎榜'—limit-up/limit-down board data) indicates retrieval of existing data.

From the tool's definition Tool name 'get_lhb_detail' follows the 'get_*' naming pattern consistent with sibling tools (get_adjust_factor_data, get_all_stock, get_balance_data, etc.). Server description indicates it provides data query services ('数据查询') for A-share market information.

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

How to control get_lhb_detail

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

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

get_lhb_detail 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 A Share — 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.

Related tools and policies

Go deeper

Questions about get_lhb_detail

What does the get_lhb_detail tool do? +

get_lhb_detail. It is categorised as a Read tool in the A Share MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_lhb_detail? +

Register the A Share MCP server in PolicyLayer and add a rule for get_lhb_detail: 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 A Share. Nothing to install.

What risk level is get_lhb_detail? +

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

Can I rate-limit get_lhb_detail? +

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

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

get_lhb_detail is provided by the A Share MCP server (shouldnotappearcalm/a-share-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every A Share tool call.

Start from A Share, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

55 A Share tools catalogued and risk-classified — across an index of 43,000+ 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.