AI agents invoke open_page to trigger actions in DaVinci Resolve MCP Server. 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 triggers an operation in DaVinci Resolve (navigating to a specific page/workspace), which is an external application action. It doesn't read data, write/create content, or destroy anything — it executes a UI navigation command in the software. The blast radius is low since it only changes which page is displayed.
From the tool's definition "Open a specific page in DaVinci Resolve" — triggers a UI navigation action in an external application
Documented attack patterns abuse exactly the kind of access open_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for open_page:
{
"version": "1",
"default": "deny",
"tools": {
"open_page": {
"limits": [
{
"counter": "open_page_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a specific page in DaVinci Resolve. It is categorised as a Execute tool in the DaVinci Resolve MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DaVinci Resolve MCP Server MCP server in PolicyLayer and add a rule for open_page: 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 DaVinci Resolve MCP Server. Nothing to install.
open_page 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 open_page 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 open_page. 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.
open_page is provided by the DaVinci Resolve MCP Server MCP server (tooflex/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DaVinci Resolve MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 DaVinci Resolve MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.