AI agents call get_stock_estimate_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.
The tool retrieves historical stock estimates, consistent with other read-only data access tools on this financial data server. The description is empty, but the naming pattern and server context strongly indicate passive data retrieval with no side effects. No ability to execute trades, modify data, or trigger external operations.
From the tool's definition Tool name 'get_stock_estimate_history' indicates retrieval of historical estimate data. Sibling tools (get_economic_indicator, get_etf_list, get_exchange_list, get_exchange_stocks) are all read-only data retrieval tools.
Attacks that exploit this kind of access
get_stock_estimate_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_estimate_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_estimate_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_estimate_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_estimate_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_estimate_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 →