Get the story evolution timeline for a living brief — versioned updates, confidence changes, and new sources over time. WHEN TO USE: To see how a story developed over time. Requires a brief ID from search/feed. RETURNS: Array of timeline entries with version number, timestamp, summary, confidence...
AI agents call veroq_timeline 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_timeline is a data retrieval tool that queries historical versions of brief information. It returns structured timeline data with no side effects, no mutations, and no irreversible operations. While the server handles financial data, this specific tool only reads and presents existing timeline information without making trades, moving money, or executing transactions.
From the tool's definition Tool retrieves and queries data: 'Get the story evolution timeline', 'versioned updates', 'RETURNS: Array of timeline entries' — no creation, modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Get the story evolution timeline for a living brief — versioned updates, confidence changes, and new sources over time. WHEN TO USE: To see how a story developed over time. Requires a brief ID from search/feed. RETURNS: Array of timeline entries with version number, timestamp, summary, confidence score, changes, and new 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_timeline: 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_timeline 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_timeline 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_timeline. 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_timeline 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 →