runtime_anim_get_state
Read the playback state of a LIVE AnimationPlayer (read-only): current animation, whether it is playing, position, length, speed scale, and the list of available animations.
This record as markdown: /tools/breakpoint-mcp/runtime-anim-get-state.md
What runtime_anim_get_state does on Breakpoint
AI agents call runtime_anim_get_state to retrieve information from Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to an AnimationPlayer node in the running scene |
peer | string | — | Target a headless peer by id (from runtime_spawn_peers). Omit to address the default running game. |
Parameters from the server's own tool schema.
Why runtime_anim_get_state is rated Low
This tool only queries and retrieves information about an AnimationPlayer's current state with no side effects, modifications, or reversible changes. It is a straightforward read operation on a live object's state, making it the safest category. Low severity because misuse would only expose animation metadata with no impact on system integrity or data.
From the tool's definition Tool description explicitly states 'Read the playback state' and '(read-only)'. It retrieves current animation, playback status, position, length, speed scale, and available animations list without modifying any data.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs runtime_anim_get_state safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For runtime_anim_get_state, this is the rule to start with:
runtime_anim_get_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every runtime_anim_get_state call is checked against it from then on.
Questions about runtime_anim_get_state
Read the playback state of a LIVE AnimationPlayer (read-only): current animation, whether it is playing, position, length, speed scale, and the list of available animations. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
runtime_anim_get_state accepts 2 parameters: path, peer. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for runtime_anim_get_state: 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 Breakpoint. Nothing to install.
runtime_anim_get_state 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 runtime_anim_get_state 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 runtime_anim_get_state. 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.
runtime_anim_get_state is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue