AI agents call get_historical_data to retrieve information from Angel One MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical market data with no capability to modify, delete, or execute transactions. This is a straightforward data retrieval operation with minimal security risk—market data is typically non-sensitive or publicly available. No financial transactions, code execution, or data modification occurs.
From the tool's definition Tool name 'get_historical_data' combined with server description stating it 'retrieve[s] historical market data and portfolio information' indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access get_historical_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Angel One MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_historical_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_historical_data": {}
}
}get_historical_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_historical_data. It is categorised as a Read tool in the Angel One MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Angel One MCP Server MCP server in PolicyLayer and add a rule for get_historical_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 Angel One MCP Server. Nothing to install.
get_historical_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_historical_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_historical_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_historical_data is provided by the Angel One MCP Server MCP server (rohandoshi21/angleone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Angel One MCP Server, 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.
3 Angel One MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.