Low Risk

rebalancing_history

获取组合历史交易信息 Args: cube_symbol: 组合代码

How to control rebalancing_history ↓

What rebalancing_history does on Xueqiu MCP

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

Low Risk

Why rebalancing_history needs a policy

This tool queries and returns historical trading records for a portfolio. It performs a read-only operation that retrieves past transaction data without any side effects, modifications, or ability to execute trades. The minimal blast radius of misuse is limited to exposure of historical transaction information, which is why severity is low.

From the tool's definition The tool description is '获取组合历史交易信息' (retrieve portfolio historical transaction information). The function retrieves historical data with a single read-only parameter (cube_symbol: portfolio code).

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

How to control rebalancing_history

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

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

rebalancing_history 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 Xueqiu MCP — 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 rebalancing_history

What does the rebalancing_history tool do? +

获取组合历史交易信息 Args: cube_symbol: 组合代码. It is categorised as a Read tool in the Xueqiu MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on rebalancing_history? +

Register the Xueqiu MCP server in PolicyLayer and add a rule for rebalancing_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 Xueqiu MCP. Nothing to install.

What risk level is rebalancing_history? +

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

Can I rate-limit rebalancing_history? +

Yes. Add a rate_limit block to the rebalancing_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.

How do I block rebalancing_history completely? +

Set action: deny in the PolicyLayer policy for rebalancing_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.

What MCP server provides rebalancing_history? +

rebalancing_history is provided by the Xueqiu MCP server (liqiongyu/xueqiu_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Xueqiu MCP tool call.

Start from Xueqiu MCP, 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.

45 Xueqiu MCP 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.