8 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Write operations (veo_image_to_video, veo_text_to_video) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Intercept sits between your agent and Mcp Veo. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @acedatacloud-mcp/mcp-veo veo_image_to_video:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
veo_get_1080p:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Mcp Veo server has 2 write tools including veo_image_to_video, veo_text_to_video. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
8 tools across 2 categories: Read, Write. 6 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the Mcp Veo server directly, prefix it with Intercept: intercept -c acedatacloud-mcp-mcp-veo.yaml -- npx -y @acedatacloud-mcp/mcp-veo. Download a pre-built policy from policylayer.com/policies/acedatacloud-mcp-mcp-veo and adjust the limits to match your use case.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init