install_library · Arduino MCP Server MCP: Risk & Policy

WHAT IT DOES

What install_library does on Arduino MCP Server

AI agents use install_library to create or update resources in Arduino MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Arduino MCP Server environment.

WHY IT NEEDS A POLICY

Why install_library needs a policy

Installing a library modifies the project environment and file system by adding new code/dependencies, which is reversible (can be uninstalled). This is a Write operation rather than Read. Severity is high because a malicious agent could install compromised or malicious libraries that execute arbitrary code during compilation or runtime, potentially compromising the user's Arduino projects and deployed devices.

From the tool's definition Tool name 'install_library' indicates package/dependency installation. Sibling tools show this is an Arduino CLI server where 'install_core' also modifies the development environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_library Rate-limited

install_library stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_library": {
      "limits": [
        {
          "counter": "install_library_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_library

What does the install_library tool do? +

install_library. 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 install_library? +

Register the Arduino MCP Server MCP server in PolicyLayer and add a rule for install_library: 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_library? +

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

Can I rate-limit install_library? +

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

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

install_library 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.