Full background research on a topic — aggregates briefs, entities, timeline, and related data. WHEN TO USE: When you need comprehensive background on a topic before answering a complex question. Broader than veroq_ask — returns raw context rather than a synthesized answer. RETURNS: Aggregated bri...
AI agents call veroq_context 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_context performs background research aggregation only—it queries and retrieves existing financial and market data without modifying, executing code, or making financial transactions. The 3-credit cost is a consumption metric, not an indication of side effects. This is a classic Read operation: fetch and present information.
From the tool's definition Tool description states it 'aggregates briefs, entities, timeline, and related data' and 'returns aggregated briefs, entity profiles, timeline of events, and related topics.' These are all retrieval and read operations with no modification, deletion, or…
Attacks that exploit this kind of access
Full background research on a topic — aggregates briefs, entities, timeline, and related data. WHEN TO USE: When you need comprehensive background on a topic before answering a complex question. Broader than veroq_ask — returns raw context rather than a synthesized answer. RETURNS: Aggregated briefs, entity profiles, timeline of events, and related topics. COST: 3 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_context: 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_context 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_context 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_context. 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_context 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 →