Low Risk

get_historical_k_data

get_historical_k_data

How to control get_historical_k_data ↓

What get_historical_k_data does on Stockreport

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

Low Risk

Why get_historical_k_data needs a policy

This tool retrieves historical stock price data (K-data refers to candlestick/OHLCV data in financial contexts). No description is provided, which slightly lowers confidence, but the naming convention and server context strongly indicate a passive data retrieval operation with no side effects. It does not execute trades, modify data, delete records, or trigger external operations.

From the tool's definition Tool name 'get_historical_k_data' follows a retrieval pattern ('get_') consistent with sibling tools like 'get_adjust_factor_data', 'get_balance_data', 'get_dividend_data', which are all data-fetching operations.

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

How to control get_historical_k_data

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

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

get_historical_k_data 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 Stockreport — 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_historical_k_data

What does the get_historical_k_data tool do? +

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

How do I enforce a policy on get_historical_k_data? +

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

What risk level is get_historical_k_data? +

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

Can I rate-limit get_historical_k_data? +

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

How do I block get_historical_k_data completely? +

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

What MCP server provides get_historical_k_data? +

get_historical_k_data is provided by the Stockreport MCP server (jamesdingai/stockreport-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stockreport tool call.

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

34 Stockreport 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.