inputmap_list

List all project-defined input actions (ProjectSettings input/*) with their deadzone and events (class + human-readable text). Read-only.

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/inputmap-list.md

WHAT IT DOES

What inputmap_list does on Breakpoint

AI agents call inputmap_list 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 inputmap_list is rated Low

This tool queries and returns information about input mappings without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation with no side effects, fitting the Read category. The low severity reflects minimal risk from exposing this informational interface.

From the tool's definition Tool description explicitly states 'Read-only' and lists its function as retrieving project-defined input actions with their properties (deadzone and events). The verb 'List' and the descriptor 'Read-only' confirm it retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

inputmap_list Allowed

inputmap_list 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": {
    "inputmap_list": {}
  }
}

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 inputmap_list call is checked against it from then on.

FAQ

Questions about inputmap_list

What does the inputmap_list tool do? +

List all project-defined input actions (ProjectSettings input/*) with their deadzone and events (class + human-readable text). Read-only. 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 inputmap_list? +

Register the Breakpoint MCP server in PolicyLayer and add a rule for inputmap_list: 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 inputmap_list? +

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

Can I rate-limit inputmap_list? +

Yes. Add a rate_limit block to the inputmap_list 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 inputmap_list completely? +

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

inputmap_list 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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