Compare how different news sources cover the same topic, with per-source bias analysis and synthesis. WHEN TO USE: When you need to understand media bias or see how coverage of an event differs across outlets. RETURNS: Topic headline, VEROQ confidence/bias scores, per-source analysis, and overall...
AI agents call veroq_compare 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_compare retrieves and analyzes news coverage data across sources to identify bias patterns and differences in reporting. This is fundamentally a query/search operation with no side effects—it does not create, modify, delete, or execute external operations. The tool synthesizes existing information rather than acting upon it.
From the tool's definition Tool description states it "Compare[s] how different news sources cover the same topic" and "RETURNS: Topic headline, VEROQ confidence/bias scores, per-source analysis, and overall synthesis." These are read operations that retrieve and analyze existing news…
Attacks that exploit this kind of access
Compare how different news sources cover the same topic, with per-source bias analysis and synthesis. WHEN TO USE: When you need to understand media bias or see how coverage of an event differs across outlets. RETURNS: Topic headline, VEROQ confidence/bias scores, per-source analysis, and overall synthesis. 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_compare: 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_compare 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_compare 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_compare. 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_compare 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 →