Biggest signal changes in the last cycle — tickers where the signal moved most. WHEN TO USE: To identify which tickers had the biggest change in buy/sell signals recently. Good for momentum or reversal detection. RETURNS: Array of tickers with previous and current signal scores and the delta. COS...
AI agents call veroq_fast_movers 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.
This tool queries market signal data to identify momentum/reversal opportunities. It has no side effects: it does not execute trades, modify data, delete records, or commit financial obligations. The server's financial context (trading signals, market data) does not elevate a read-only retrieval operation beyond the Read category.
From the tool's definition Tool retrieves 'Biggest signal changes in the last cycle' and returns 'Array of tickers with previous and current signal scores and the delta' — pure data retrieval with no modifications, deletions, or financial transactions.
Attacks that exploit this kind of access
Biggest signal changes in the last cycle — tickers where the signal moved most. WHEN TO USE: To identify which tickers had the biggest change in buy/sell signals recently. Good for momentum or reversal detection. RETURNS: Array of tickers with previous and current signal scores and the delta. 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_movers: 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_movers 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_movers 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_movers. 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_movers 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 →