Screen stocks based on filters with validation and confidence scores. Supports multiple filter criteria.
AI agents call screener to retrieve information from Yfnhanced without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The screener tool filters and retrieves stock data based on user-defined criteria, which is a read-only operation. It returns analysis results without modifying any data, executing code, or moving money.
From the tool's definition Tool name 'screener' and description 'Screen stocks based on filters with validation and confidence scores' indicate data retrieval and querying functionality. No creation, modification, deletion, code execution, or financial transactions are performed.
Documented attack patterns abuse exactly the kind of access screener gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Yfnhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for screener:
{
"version": "1",
"default": "deny",
"tools": {
"screener": {}
}
}screener is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Screen stocks based on filters with validation and confidence scores. Supports multiple filter criteria. It is categorised as a Read tool in the Yfnhanced MCP Server, which means it retrieves data without modifying state.
Register the Yfnhanced MCP server in PolicyLayer and add a rule for screener: 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 Yfnhanced. Nothing to install.
screener 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 screener 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 screener. 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.
screener is provided by the Yfnhanced MCP server (kanishka-namdeo/yfnhanced-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Yfnhanced, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Yfnhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.