get_adjust_factor_data
AI agents call get_adjust_factor_data 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.
This is a query/read operation following the pattern of all sibling tools on the server, which provides financial data queries. No evidence of write, execute, destructive, or financial operations. Adjustment factors in stock data are typically multipliers used to normalize historical prices for stock splits or dividends—purely informational data retrieval with no side effects.
From the tool's definition Tool name 'get_adjust_factor_data' contains the verb 'get', indicating data retrieval. Empty description reduces specificity but context from server purpose (providing A-share real-time quotes, historical K-lines, financial reports, technical indicators) and…
Documented attack patterns abuse exactly the kind of access get_adjust_factor_data gives an agent:
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_adjust_factor_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_adjust_factor_data": {}
}
}get_adjust_factor_data 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_adjust_factor_data. It is categorised as a Read tool in the A Share MCP Server, which means it retrieves data without modifying state.
Register the A Share MCP server in PolicyLayer and add a rule for get_adjust_factor_data: 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.
get_adjust_factor_data 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_adjust_factor_data 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_adjust_factor_data. 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_adjust_factor_data 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.
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.