Screen stocks or crypto by combining technical indicators, sentiment, and fundamental filters. WHEN TO USE: To find assets matching specific criteria (e.g. oversold tech stocks, high-volume bearish crypto). Use veroq_screener_presets for pre-built strategies. RETURNS: Matching assets with symbol,...
AI agents call veroq_screener to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
veroq_screener retrieves and filters existing market data without modifying, creating, deleting, or executing transactions. It performs a read-only search operation across financial datasets to match assets against specified technical and sentiment criteria. No financial transactions, code execution, or irreversible modifications occur. The tool returns informational results only.
From the tool's definition Tool description states it 'Screen stocks or crypto by combining technical indicators, sentiment, and fundamental filters' and 'RETURNS: Matching assets with symbol, price, change%, RSI, MACD signal, sentiment, and volume.' The primary function is data…
Attacks that exploit this kind of access
Screen stocks or crypto by combining technical indicators, sentiment, and fundamental filters. WHEN TO USE: To find assets matching specific criteria (e.g. oversold tech stocks, high-volume bearish crypto). Use veroq_screener_presets for pre-built strategies. RETURNS: Matching assets with symbol, price, change%, RSI, MACD signal, sentiment, and volume. COST: 5 credits. EXAMPLE: {. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_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 Veroq. Nothing to install.
veroq_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 veroq_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 veroq_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.
veroq_screener is provided by the Veroq MCP server (veroq-ai/veroq-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 →