Get a composite trading signal score for a ticker based on sentiment, momentum, coverage volume, and event proximity. WHEN TO USE: For a quick bull/bear signal on a ticker. Use veroq_ticker_analysis for deeper context behind the signal. RETURNS: Composite score, signal (strong_bullish to strong_b...
AI agents call veroq_ticker_score 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 is a Read operation: it queries financial data and returns a bull/bear signal for informational purposes. However, severity is medium rather than low because the output directly informs financial trading decisions.
From the tool's definition Tool retrieves and returns a composite trading signal score with components (sentiment, momentum, volume, events) — it queries market data and returns analysis without modifying, creating, or executing trades.
Attacks that exploit this kind of access
Get a composite trading signal score for a ticker based on sentiment, momentum, coverage volume, and event proximity. WHEN TO USE: For a quick bull/bear signal on a ticker. Use veroq_ticker_analysis for deeper context behind the signal. RETURNS: Composite score, signal (strong_bullish to strong_bearish), and component breakdown (sentiment, momentum, volume, events with weights). COST: 2 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_ticker_score: 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_ticker_score 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_ticker_score 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_ticker_score. 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_ticker_score 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 →