ensure_core_installed

Ensure the Arduino core required by a board FQBN is installed. Can auto-install via `arduino-cli core install`.

Part of the Arduino MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents use ensure_core_installed to create or modify resources in Arduino MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON ENSURE_CORE_INSTALLED

Without a policy, an AI agent could call ensure_core_installed repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Arduino MCP Server.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

arduino-mcp-server.yaml

tools:
  ensure_core_installed:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Arduino MCP Server policy for all 21 tools.

// DETAILS

Tool Name ensure_core_installed

Category Write

MCP Server Arduino MCP Server MCP Server

Risk Level Medium

// MORE ARDUINO MCP SERVER TOOLS

Execute compile_sketch Execute safety_preflight Write install_arduino_cli Write serial_close_session Write serial_open_session Write serial_write Write upload_and_wait_ready Write upload_sketch

View all 21 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like ensure_core_installed have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the ensure_core_installed tool do? +

Ensure the Arduino core required by a board FQBN is installed. Can auto-install via `arduino-cli core install`.. It is categorised as a Write tool in the Arduino MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ensure_core_installed? +

Add a rule in your Intercept YAML policy under the tools section for ensure_core_installed. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Arduino MCP Server MCP server.

What risk level is ensure_core_installed? +

ensure_core_installed is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ensure_core_installed? +

Yes. Add a rate_limit block to the ensure_core_installed rule in your Intercept 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 ensure_core_installed completely? +

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

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

ensure_core_installed

Let agents act without letting them run wild.