Get notable events detected across intelligence briefs — significant developments, announcements, and inflection points. WHEN TO USE: To discover major events like product launches, policy changes, or market-moving announcements. Filter by type or subject. RETURNS: Array of events with type, subj...
AI agents call veroq_events 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 data retrieval tool that searches and filters historical event information. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The 'impact score' is a computed metric within the response, not an action taken. Confidence is high due to clear descriptive language indicating query/retrieval functionality.
From the tool's definition Tool retrieves and queries notable events data from intelligence briefs—'Get notable events detected across intelligence briefs', 'returns Array of events'. No modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Get notable events detected across intelligence briefs — significant developments, announcements, and inflection points. WHEN TO USE: To discover major events like product launches, policy changes, or market-moving announcements. Filter by type or subject. RETURNS: Array of events with type, subject, headline, summary, impact score, detected timestamp, and related brief IDs. 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_events: 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_events 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_events 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_events. 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_events 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 →