selection_get
Return the paths of the nodes currently selected in the editor.
This record as markdown: /tools/breakpoint-mcp/selection-get.md
What selection_get does on Breakpoint
AI agents call selection_get 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.
Why selection_get is rated Low
This tool queries and returns data about the current selection state in an editor. It has no side effects, does not modify data, execute commands, delete anything, or involve financial operations. It is a straightforward read operation that retrieves information about which nodes are selected.
From the tool's definition Tool name 'selection_get' and description 'Return the paths of the nodes currently selected in the editor' indicate a query operation that retrieves editor state without modification.
Attacks that exploit this kind of access
The rule that runs selection_get 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 selection_get, this is the rule to start with:
selection_get 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 selection_get call is checked against it from then on.
Questions about selection_get
Return the paths of the nodes currently selected in the editor. It is categorised as a Read tool in the Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Breakpoint MCP server in PolicyLayer and add a rule for selection_get: 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.
selection_get 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 selection_get 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 selection_get. 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.
selection_get 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