set_frame
Set the current frame in the timeline.
This record as markdown: /tools/dwgx-blender-copilot/set-frame.md
What set_frame does on Blender Copilot MCP Server
AI agents use set_frame to create or update resources in Blender Copilot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Blender Copilot MCP Server environment.
Why set_frame is rated Medium
Setting the current frame changes the state of the timeline in Blender, which is a reversible modification (you can set it back). It does not execute code, delete data, or have financial implications. Severity is low as it only affects the current frame position.
From the tool's definition 'Set the current frame in the timeline' — modifies the animation playback position in Blender
Attacks that exploit this kind of access
The rule that runs set_frame safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Blender Copilot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_frame, this is the rule to start with:
set_frame 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Blender Copilot MCP Server, apply this rule, and every set_frame call is checked against it from then on.
Questions about set_frame
Set the current frame in the timeline. It is categorised as a Write tool in the Blender Copilot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender Copilot MCP Server MCP server in PolicyLayer and add a rule for set_frame: 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 Blender Copilot MCP Server. Nothing to install.
set_frame 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 set_frame 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 set_frame. 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.
set_frame is provided by the Blender Copilot MCP Server MCP server (dwgx/blender-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Blender Copilot MCP Server, and thousands of servers like it.
This server
Across the catalogue