AI agents call get_stock_ownership 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 ownership data about stocks, which is a read operation with no side effects. Severity is medium rather than low because ownership data can reveal material information about insider positions, major shareholders, or political/guru holdings (per server description mentioning 'insiders' and 'politicians'), which could inform investment decisions if misused by an agent.
From the tool's definition Tool name 'get_stock_ownership' indicates retrieval of ownership data. Description is empty, but context from sibling tools (get_api_usage, get_country_currency, get_economic_indicator, get_etf_list, etc.) all retrieve financial data without modification.
Attacks that exploit this kind of access
get_stock_ownership. 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_ownership: 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_ownership 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_ownership 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_ownership. 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_ownership 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 →