Get full details for a specific intelligence brief by its ID. WHEN TO USE: After finding a brief via search/feed, use this to read the full body, sources, entities, and counter-argument. RETURNS: Full brief with body text, sources (with trust levels), entities, counter-argument, and provenance (c...
AI agents call veroq_brief 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 pure retrieval operation that queries and returns existing data (intelligence brief contents) with no side effects, no data modification, no code execution, and no financial transactions. It fits squarely in the Read category as a fetch/get operation.
From the tool's definition Tool retrieves full details for a specific intelligence brief by ID, returning body text, sources, entities, counter-argument, and provenance.
Attacks that exploit this kind of access
Get full details for a specific intelligence brief by its ID. WHEN TO USE: After finding a brief via search/feed, use this to read the full body, sources, entities, and counter-argument. RETURNS: Full brief with body text, sources (with trust levels), entities, counter-argument, and provenance (confidence, bias, AI/human split). 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_brief: 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_brief 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_brief 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_brief. 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_brief 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 →