list_installed_libraries
AI agents call list_installed_libraries to retrieve information from Arduino MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about installed Arduino libraries without modifying, executing, or deleting anything. It poses minimal security risk as an information-disclosure vector, though the actual harm depends on what an agent does with the library list. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'list_installed_libraries' indicates a query/listing operation. The description is empty, but the name clearly denotes a retrieval action with no side effects.
Attacks that exploit this kind of access
list_installed_libraries. It is categorised as a Read tool in the Arduino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Arduino MCP Server MCP server in PolicyLayer and add a rule for list_installed_libraries: 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.
list_installed_libraries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_installed_libraries 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.
Set action: deny in the PolicyLayer policy for list_installed_libraries. 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.
list_installed_libraries 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →