Configure MCP conversational defaults and setup preferences. Actions: schema() -> {defaults, actions} get_defaults() -> {defaults} set_defaults(defaults?|media_analysis?|updates?|dry_run?) -> {defaults, changes} clear_defaults(keys?, dry_run?) -> {defaults, cleared} Current defaults: media_analys...
AI agents use setup to create or update resources in DaVinci Resolve MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DaVinci Resolve MCP environment.
This tool creates and modifies stored preferences and defaults within the DaVinci Resolve MCP system. While the changes are reversible (making it Write rather than Destructive), an adversarial AI agent could misconfigure analysis behavior, disable safety updates, or alter workflow defaults to facilitate subsequent malicious actions.
From the tool's definition The tool includes set_defaults() and clear_defaults() actions that modify configuration state. set_defaults() accepts parameters to change 'media_analysis' and 'updates' settings, and clear_defaults() explicitly removes stored preference keys.
Documented attack patterns abuse exactly the kind of access setup gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DaVinci Resolve MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for setup:
{
"version": "1",
"default": "deny",
"tools": {
"setup": {
"limits": [
{
"counter": "setup_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}setup stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Configure MCP conversational defaults and setup preferences. Actions: schema() -> {defaults, actions} get_defaults() -> {defaults} set_defaults(defaults?|media_analysis?|updates?|dry_run?) -> {defaults, changes} clear_defaults(keys?, dry_run?) -> {defaults, cleared} Current defaults: media_analysis.*: analysis, metadata, marker, reporting, and workflow defaults updates.*: MCP update policy, interval, and snooze defaults. It is categorised as a Write tool in the DaVinci Resolve MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DaVinci Resolve MCP server in PolicyLayer and add a rule for setup: 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. Nothing to install.
setup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the setup 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 setup. 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.
setup is provided by the DaVinci Resolve MCP server (samuelgursky/davinci-resolve-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 369 DaVinci Resolve MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
369 DaVinci Resolve MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.