AI agents call screen_securities to retrieve information from Borsa MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screening securities is a query and analysis operation that retrieves and filters existing market data without side effects. It enables users to search and view information about stocks/ETFs based on criteria, but does not create, modify, delete, or execute trades. This is a Read operation with low severity due to no financial or operational risk beyond normal market data access.
From the tool's definition Tool performs screening/filtering of securities data using presets and custom filters. Keywords indicate data retrieval: 'screen', 'presets', 'filters' with no mention of modification, deletion, execution, or financial transactions.
Attacks that exploit this kind of access
Screen stocks/ETFs with 24 presets (value, growth, dividend, sector) or custom filters. It is categorised as a Read tool in the Borsa MCP MCP Server, which means it retrieves data without modifying state.
Register the Borsa MCP server in PolicyLayer and add a rule for screen_securities: 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 Borsa MCP. Nothing to install.
screen_securities 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 screen_securities 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 screen_securities. 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.
screen_securities is provided by the Borsa MCP server (saidsurucu/borsa-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 →