editorsettings_get_set
Read an EditorSettings value by name; if 'value' is provided, write it instead (persists to the editor's global config). Reading is read-only; writing is DESTRUCTIVE (mutates the editor config) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/editorsettings-get-set.md
What editorsettings_get_set does on Breakpoint
AI agents use editorsettings_get_set to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | EditorSettings key, e.g. interface/editor/code_font_size |
value | object | — | If provided, set this value (rich types use the {"__type__":...} tagging convention) |
confirm | boolean | — | Auto-approve the write (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why editorsettings_get_set is rated Medium
The tool can both read and write editor settings. Writing persists changes to the editor's global config. While the description calls writing 'DESTRUCTIVE', config changes are typically reversible by restoring previous values, so Write is more appropriate than Destructive. The most severe applicable category for a tool that can mutate persistent configuration is Write.
From the tool's definition 'Read an EditorSettings value by name; if value is provided, write it instead (persists to the editor's global config)' and 'mutates the editor config'
Attacks that exploit this kind of access
The rule that runs editorsettings_get_set 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 editorsettings_get_set, this is the rule to start with:
editorsettings_get_set 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 Breakpoint, apply this rule, and every editorsettings_get_set call is checked against it from then on.
Questions about editorsettings_get_set
Read an EditorSettings value by name; if 'value' is provided, write it instead (persists to the editor's global config). Reading is read-only; writing is DESTRUCTIVE (mutates the editor config) — gated by confirmation. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
editorsettings_get_set accepts 3 parameters: name, value, confirm. Required: name. 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 editorsettings_get_set: 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.
editorsettings_get_set 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 editorsettings_get_set 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 editorsettings_get_set. 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.
editorsettings_get_set 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