AI agents call get_stock_indicator_history to retrieve information from Gurufocus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical stock indicator data with no side effects. The 'get_' naming convention and alignment with other retrieval-only tools on the GuruFocus MCP server indicate a passive query operation. No data is modified, deleted, or executed. Severity is low because misuse would only expose or exfiltrate financial data, not cause irreversible damage or financial harm.
From the tool's definition Tool name 'get_stock_indicator_history' indicates retrieval of historical stock indicator data. Empty description limits certainty but the 'get_' prefix and context of sibling tools (all data retrieval: get_api_usage, get_country_currency,…
Attacks that exploit this kind of access
get_stock_indicator_history. It is categorised as a Read tool in the Gurufocus MCP Server, which means it retrieves data without modifying state.
Register the Gurufocus MCP server in PolicyLayer and add a rule for get_stock_indicator_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 Gurufocus. Nothing to install.
get_stock_indicator_history 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_stock_indicator_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.
Set action: deny in the PolicyLayer policy for get_stock_indicator_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.
get_stock_indicator_history is provided by the Gurufocus MCP server (u-daveblack/gurufocus-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 →