AI agents call get_user_screeners 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 and context of a financial data API server strongly indicate this retrieves user-defined stock screener configurations rather than executing trades or modifying financial state. No description is available, which slightly lowers confidence, but the naming pattern and sibling tools consistently reflect query operations over GuruFocus financial datasets.
From the tool's definition Tool name 'get_user_screeners' and sibling tools (get_etf_list, get_exchange_stocks, get_economic_indicator) are all read-only data retrieval endpoints. The server provides financial data access without mutation capabilities.
Attacks that exploit this kind of access
get_user_screeners. 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_user_screeners: 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_user_screeners 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_user_screeners 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_user_screeners. 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_user_screeners 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 →