breakpoint_ports
Who holds each port this server dials — editor and runtime bridges, GDScript LSP and DAP, live peers: held or free, each holder's pid and program, and whether this server started it. Read-only. Use it when a launch is refused over a held port or a bridge will not answer.
This record as markdown: /tools/breakpoint-mcp/breakpoint-ports.md
What breakpoint_ports does on Breakpoint
AI agents call breakpoint_ports 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 breakpoint_ports is rated Low
Even though breakpoint_ports only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs breakpoint_ports 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 breakpoint_ports, this is the rule to start with:
breakpoint_ports 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 breakpoint_ports call is checked against it from then on.
Questions about breakpoint_ports
Who holds each port this server dials — editor and runtime bridges, GDScript LSP and DAP, live peers: held or free, each holder's pid and program, and whether this server started it. Read-only. Use it when a launch is refused over a held port or a bridge will not answer. 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 breakpoint_ports: 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.
breakpoint_ports 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 breakpoint_ports 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 breakpoint_ports. 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.
breakpoint_ports 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