Low Risk

get_screening_result

Retrieve saved screening results

How to control get_screening_result ↓

AI agents call get_screening_result to retrieve information from StockScreen MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns previously saved stock screening results. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any actions. The low severity reflects minimal risk even if misused by an AI agent, as it only exposes already-computed screening data.

From the tool's definition Tool name is 'get_screening_result' and description states 'Retrieve saved screening results' — both indicate data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_screening_result gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and StockScreen MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_screening_result:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_screening_result": {}
  }
}

get_screening_result is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register StockScreen MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_screening_result tool do? +

Retrieve saved screening results. It is categorised as a Read tool in the StockScreen MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_screening_result? +

Register the StockScreen MCP Server MCP server in PolicyLayer and add a rule for get_screening_result: 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 StockScreen MCP Server. Nothing to install.

What risk level is get_screening_result? +

get_screening_result is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_screening_result? +

Yes. Add a rate_limit block to the get_screening_result 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.

How do I block get_screening_result completely? +

Set action: deny in the PolicyLayer policy for get_screening_result. 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.

What MCP server provides get_screening_result? +

get_screening_result is provided by the StockScreen MCP Server MCP server (twolven/mcp-stockscreen). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every StockScreen MCP Server tool call.

Deterministic rules across all 4 StockScreen MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4 StockScreen MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.