AI agents call veroq_trending 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 tool retrieves and queries trending data (people, organizations, topics) without creating, modifying, deleting, or executing any operations. It has no side effects beyond returning read-only market/trending intelligence. The blast radius of misuse is minimal—an AI agent querying trending data cannot cause financial harm, data loss, or unintended executions.
From the tool's definition Tool description states 'Get trending entities' and retrieves data about mentions in the last 24 hours. No modification, deletion, or execution of commands indicated.
Attacks that exploit this kind of access
Get trending entities — people, orgs, and topics with the most mentions in the last 24 hours. WHEN TO USE: To discover what. 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_trending: 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_trending 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_trending 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_trending. 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_trending 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 →