add_breakpoint · MCPEmulate MCP: Risk & Policy

WHAT IT DOES

What add_breakpoint does on MCPEmulate

AI agents invoke add_breakpoint to trigger actions in MCPEmulate. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why add_breakpoint needs a policy

Adding a breakpoint modifies the execution control flow of an emulated CPU session. It is a write/execute-level operation that affects runtime behavior, not merely reading data. Within an emulation context, misuse could interfere with analysis sessions or be used to manipulate execution tracing. It doesn't delete data or move money, but it does affect execution behavior, placing it in Execute.

From the tool's definition 'Add a breakpoint at the given address' — modifies the execution state of an emulation session by setting a breakpoint that alters how/where code execution halts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_breakpoint Rate-limited

add_breakpoint stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_breakpoint": {
      "limits": [
        {
          "counter": "add_breakpoint_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCPEmulate, so you can run agents against it safely.

FAQ

Questions about add_breakpoint

What does the add_breakpoint tool do? +

Add a breakpoint at the given address. It is categorised as a Execute tool in the MCPEmulate MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on add_breakpoint? +

Register the MCPEmulate MCP server in PolicyLayer and add a rule for add_breakpoint: 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 MCPEmulate. Nothing to install.

What risk level is add_breakpoint? +

add_breakpoint is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit add_breakpoint? +

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

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

add_breakpoint is provided by the MCPEmulate MCP server (labguy94/mcpemulate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.