editor_get_state

Return the currently edited scene, its root type/path, and the current node selection.

SERVERBreakpoint SOURCEbreakpoint-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/breakpoint-mcp/editor-get-state.md

WHAT IT DOES

What editor_get_state does on Breakpoint

AI agents call editor_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.

RISK

Why editor_get_state is rated Low

This tool queries and returns information about the current state of an editor (scene, root type/path, node selection) without creating, modifying, or deleting any data. It is a pure read operation with minimal blast radius if misused by an AI agent—it cannot corrupt data or trigger unwanted actions.

From the tool's definition Tool name 'editor_get_state' and description 'Return the currently edited scene, its root type/path, and the current node selection' indicate a retrieval operation with no modification or side effects.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_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 editor_get_state, this is the rule to start with:

editor_get_state Allowed

editor_get_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_get_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every editor_get_state call is checked against it from then on.

FAQ

Questions about editor_get_state

What does the editor_get_state tool do? +

Return the currently edited scene, its root type/path, and the current node selection. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_get_state? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for editor_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.

What risk level is editor_get_state? +

editor_get_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit editor_get_state? +

Yes. Add a rate_limit block to the editor_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.

How do I block editor_get_state completely? +

Set action: deny in the PolicyLayer policy for editor_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.

What MCP server provides editor_get_state? +

editor_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.

KEEP EXPLORING

More on Breakpoint, and thousands of servers like it.

This server

All 274 Breakpoint tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →