Get historical K-bar data
AI agents call get_kbars to retrieve information from Shioaji MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical price/volume data (K-bars are OHLCV candlestick bars) for analysis purposes. It has no side effects, does not execute trades, move funds, or modify any state. It is a pure read operation on market data. Even in the context of a trading platform, querying historical data poses minimal risk compared to order execution or account modification tools on the same server.
From the tool's definition Tool name 'get_kbars' and description 'Get historical K-bar data' indicate data retrieval without modification. K-bars (candlestick data) are historical market data used for analysis.
Attacks that exploit this kind of access
Get historical K-bar data. It is categorised as a Read tool in the Shioaji MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Shioaji MCP Server MCP server in PolicyLayer and add a rule for get_kbars: 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 Shioaji MCP Server. Nothing to install.
get_kbars 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_kbars 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_kbars. 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_kbars is provided by the Shioaji MCP Server MCP server (offbeat-studio/shioaji-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →