Get a diff of changes to a living brief since a given time — additions, removals, and modifications between versions. WHEN TO USE: To see exactly what changed in a brief since a specific timestamp. Requires a brief ID. RETURNS: Version range, confidence change, field-level changes (old/new values...
AI agents call veroq_diff 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 tool that queries version history and returns a comparative view (diff) of changes. The tool has no side effects—it reads and presents data in a different format. While the server provides financial intelligence, this specific tool only accesses and displays historical information about brief modifications without executing trades, modifying positions, or triggering external actions.
From the tool's definition The tool 'Get a diff of changes to a living brief since a given time' retrieves and compares historical versions of a brief, returning 'Version range, confidence change, field-level changes (old/new values), and newly added sources.' It performs no mutations,…
Attacks that exploit this kind of access
Get a diff of changes to a living brief since a given time — additions, removals, and modifications between versions. WHEN TO USE: To see exactly what changed in a brief since a specific timestamp. Requires a brief ID. RETURNS: Version range, confidence change, field-level changes (old/new values), and newly added sources. 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_diff: 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_diff 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_diff 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_diff. 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_diff 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 →