Run a VEROQ AI agent by its slug — pre-built workflows combining multiple data sources and analysis steps. WHEN TO USE: For complex multi-step analysis tasks like portfolio reviews, due diligence, or market scans. Agents automate what would take many individual tool calls. RETURNS: Agent name, ex...
AI agents invoke veroq_run_agent to trigger actions in Veroq. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes external AI agent workflows whose effects depend on which agent slug is specified as an argument. While the tool itself performs data analysis rather than destructive operations, it triggers automated multi-step processes that could make financial decisions or recommendations.
From the tool's definition Tool runs pre-built workflows ('Run a VEROQ AI agent') that combine multiple data sources and analysis steps. Description explicitly states it automates complex multi-step analysis tasks and returns execution steps with status.
Attacks that exploit this kind of access
Run a VEROQ AI agent by its slug — pre-built workflows combining multiple data sources and analysis steps. WHEN TO USE: For complex multi-step analysis tasks like portfolio reviews, due diligence, or market scans. Agents automate what would take many individual tool calls. RETURNS: Agent name, execution steps (with status/summary per step), final output or structured result, and credits used. COST: 5-100 credits (varies by agent complexity). EXAMPLE: {. It is categorised as a Execute tool in the Veroq MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_run_agent: 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_run_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the veroq_run_agent 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_run_agent. 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_run_agent 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 →