inputmap_add_event
Append an input event to an existing project input action. 'event' is { type: key|mouse_button|joy_button|joy_motion, ... } — key: keycode or physical_keycode as a name like "A"/"Space" or an int; mouse_button/joy_button: button_index; joy_motion: axis + axis_value. Set save=true to persist. DEST...
This record as markdown: /tools/breakpoint-mcp/inputmap-add-event.md
What inputmap_add_event does on Breakpoint
AI agents use inputmap_add_event 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 | Existing action name (without the input/ prefix) |
save | boolean | — | Persist to project.godot (default false) |
event | object | Yes | Input event descriptor |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why inputmap_add_event is rated Medium
The tool appends/adds an input event mapping to a project action, which is a write/modification operation. While the description labels it 'DESTRUCTIVE', the actual operation is adding a new event to an existing action (reversible by removing the event), not deleting or overwriting data irreversibly.
From the tool's definition Append an input event to an existing project input action... Set save=true to persist. DESTRUCTIVE — gated by confirmation.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs inputmap_add_event 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_add_event, this is the rule to start with:
inputmap_add_event 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 inputmap_add_event call is checked against it from then on.
Questions about inputmap_add_event
Append an input event to an existing project input action. 'event' is { type: key|mouse_button|joy_button|joy_motion, ... } — key: keycode or physical_keycode as a name like "A"/"Space" or an int; mouse_button/joy_button: button_index; joy_motion: axis + axis_value. Set save=true to persist. DESTRUCTIVE — 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.
inputmap_add_event accepts 4 parameters: name, save, event, confirm. Required: name, event. 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_add_event: 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_add_event 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 inputmap_add_event 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_add_event. 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_add_event 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