Get a sector overview with aggregate sentiment scores and brief counts across all market sectors. WHEN TO USE: For a macro view of which sectors have the most bullish or bearish news coverage. Good for sector rotation analysis. RETURNS: Per-sector data: ticker count, brief count, average sentimen...
AI agents call veroq_sectors 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 data retrieval tool that queries and returns market sentiment analysis and sector statistics. It has no side effects—it neither modifies data, executes operations, nor commits financial obligations. The use case ('macro view of which sectors have the most bullish or bearish news') confirms it supports research and analysis only.
From the tool's definition Tool retrieves sector overview data with sentiment scores and brief counts. Returns read-only aggregate data: ticker count, brief count, average sentiment, and top tickers. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
Get a sector overview with aggregate sentiment scores and brief counts across all market sectors. WHEN TO USE: For a macro view of which sectors have the most bullish or bearish news coverage. Good for sector rotation analysis. RETURNS: Per-sector data: ticker count, brief count, average sentiment, and top tickers with individual sentiment. 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_sectors: 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_sectors 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_sectors 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_sectors. 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_sectors 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 →