run · Jlink MCP: Risk & Policy

WHAT IT DOES

What run does on Jlink

AI agents invoke run to trigger actions in Jlink. 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 run needs a policy

This tool triggers external code execution on a microcontroller device. The effects are dynamic and depend on the target firmware logic—it could perform arbitrary hardware operations (GPIO, timers, communications, memory writes). While not irreversible in itself (Destructive), it executes untrusted code paths.

From the tool's definition Tool 'run' continues target program execution on a microcontroller. The server description states it 'enables AI assistants like Claude to directly debug microcontrollers via JLink, supporting breakpoints, single-step, memory/register access, variable…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run Rate-limited

run 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": {
    "run": {
      "limits": [
        {
          "counter": "run_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 Jlink, so you can run agents against it safely.

FAQ

Questions about run

What does the run tool do? +

继续执行目标程序（从当前 PC 位置继续运行）。. It is categorised as a Execute tool in the Jlink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run? +

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

What risk level is run? +

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

Can I rate-limit run? +

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

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

run is provided by the Jlink MCP server (xun123456/jlink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.