Pre-computed buy/sell signals across 78 tickers — refreshed every cycle. WHEN TO USE: For a quick overview of all active signals without running individual ticker analyses. Good for scanning opportunities. RETURNS: Array of tickers with signal direction (buy/sell/hold), score, and contributing fa...
AI agents call veroq_fast_signals 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_fast_signals retrieves and presents pre-computed trading signals without side effects. While the signals inform financial decisions, the tool itself performs no financial operations, does not execute trades, and does not modify any state. It is purely informational data retrieval, making it a Read operation with low risk from direct misuse.
From the tool's definition Tool returns 'Array of tickers with signal direction (buy/sell/hold), score, and contributing factors' — a read-only query of pre-computed market signals. No creation, modification, deletion, code execution, or financial transactions occur.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Pre-computed buy/sell signals across 78 tickers — refreshed every cycle. WHEN TO USE: For a quick overview of all active signals without running individual ticker analyses. Good for scanning opportunities. RETURNS: Array of tickers with signal direction (buy/sell/hold), score, and contributing factors. COST: 1 credit. 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_fast_signals: 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_fast_signals 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_fast_signals 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_fast_signals. 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_fast_signals 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 →