inputmap_erase_action
Remove a project input action (ProjectSettings input/<name>). Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/inputmap-erase-action.md
What inputmap_erase_action does on Breakpoint
AI agents call inputmap_erase_action to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Action name (without the input/ prefix) |
save | boolean | — | Persist to project.godot (default false) |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
Parameters from the server's own tool schema.
Why inputmap_erase_action is rated Critical
This tool irreversibly deletes input action configurations from a Godot project. Once erased and persisted to disk, the configuration cannot be recovered through the tool's normal operation. This is a destructive operation that modifies project state permanently. The 'gated by confirmation' note indicates recognition of the risk, but the capability remains destructive.
From the tool's definition Tool description explicitly states 'Remove a project input action' and marks it 'DESTRUCTIVE'. The name 'erase_action' indicates deletion. Description notes 'Set save=true to persist to project.godot', confirming the action is irreversible when saved.
Attacks that exploit this kind of access
The rule that runs inputmap_erase_action 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 inputmap_erase_action, this is the rule to start with:
inputmap_erase_action is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every inputmap_erase_action call is checked against it from then on.
Questions about inputmap_erase_action
Remove a project input action (ProjectSettings input/<name>). Set save=true to persist to project.godot. DESTRUCTIVE — gated by confirmation. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
inputmap_erase_action accepts 3 parameters: name, save, 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 inputmap_erase_action: 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.
inputmap_erase_action is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the inputmap_erase_action 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 inputmap_erase_action. 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.
inputmap_erase_action 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.
Across the catalogue