AI agents call get_guru_aggregated 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 'get_' prefix is a strong signal of read-only behavior. Sibling tools (get_api_usage, get_country_currency, get_economic_indicator, etc.) are all retrieval functions. The tool appears to retrieve aggregated guru data without side effects. Low severity because read operations pose minimal risk; blast radius limited to data disclosure. Confidence reduced from 0.9 to 0.85 due to empty description.
From the tool's definition Tool name 'get_guru_aggregated' strongly suggests data retrieval/aggregation. The empty description limits certainty, but naming convention and server context (GuruFocus financial data exposure) indicate this fetches aggregated guru information rather than…
Attacks that exploit this kind of access
get_guru_aggregated. 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_guru_aggregated: 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_guru_aggregated 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_guru_aggregated 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_guru_aggregated. 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_guru_aggregated 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 →