install_core · Arduino MCP Server MCP: Risk & Policy

WHAT IT DOES

What install_core does on Arduino MCP Server

AI agents invoke install_core to trigger actions in Arduino MCP Server. 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 install_core needs a policy

Installing a core (board support package) triggers an external operation — downloading and installing software packages via Arduino CLI. This is an Execute-level action as it modifies system state by installing packages, though it is generally reversible. The empty description reduces confidence, but the name and server context strongly suggest this installs an Arduino board core.

From the tool's definition Tool name 'install_core' on an Arduino MCP server context alongside sibling tools like 'install_library', 'list_installed_cores'. Empty description lowers confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_core Rate-limited

install_core 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": {
    "install_core": {
      "limits": [
        {
          "counter": "install_core_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 Arduino MCP Server, so you can run agents against it safely.

FAQ

Questions about install_core

What does the install_core tool do? +

install_core. It is categorised as a Execute tool in the Arduino MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on install_core? +

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

What risk level is install_core? +

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

Can I rate-limit install_core? +

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

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

install_core is provided by the Arduino MCP Server MCP server (niradler/arduino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.