List all available Veo API actions and corresponding tools. Reference guide for what each action does and which tool to use. Helpful for understanding the full capabilities of the Veo MCP. Returns: Categorized list of all actions and their corresponding tools.
Part of the Mcp Veo server.
Free to start. No card required.
AI agents call veo_list_actions to retrieve information from Mcp Veo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though veo_list_actions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"veo_list_actions": {}
}
}See the full Mcp Veo policy for all 8 tools.
These attack patterns abuse exactly the kind of access veo_list_actions gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List all available Veo API actions and corresponding tools. Reference guide for what each action does and which tool to use. Helpful for understanding the full capabilities of the Veo MCP. Returns: Categorized list of all actions and their corresponding tools.. It is categorised as a Read tool in the Mcp Veo MCP Server, which means it retrieves data without modifying state.
Register the Mcp Veo MCP server in PolicyLayer and add a rule for veo_list_actions: 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 Mcp Veo. Nothing to install.
veo_list_actions 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 veo_list_actions 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 veo_list_actions. 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.
veo_list_actions is provided by the Mcp Veo MCP server (acedatacloud-mcp/mcp-veo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mcp Veo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.