Get all intelligence briefs mentioning a specific entity (person, company, location, etc.). WHEN TO USE: When tracking coverage of a specific person, organization, or place across all briefs. RETURNS: Array of briefs mentioning the entity, with headline, confidence, category, and summary. COST: 1...
AI agents call veroq_entities 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_entities is a search/retrieval function that filters and returns pre-existing intelligence briefs by entity reference. It has no side effects on data—it only reads and aggregates information.
From the tool's definition Tool retrieves and queries existing intelligence briefs mentioning a specific entity; returns array of briefs with metadata (headline, confidence, category, summary). No modification, deletion, or execution described.
Attacks that exploit this kind of access
Get all intelligence briefs mentioning a specific entity (person, company, location, etc.). WHEN TO USE: When tracking coverage of a specific person, organization, or place across all briefs. RETURNS: Array of briefs mentioning the entity, with headline, confidence, category, and summary. 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_entities: 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_entities 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_entities 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_entities. 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_entities 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 →