list_installed_cores

list_installed_cores

Server Arduino MCP Server niradler/arduino-mcp
Category Read
Risk class Low
Parameters 00 required

What list_installed_cores does on Arduino MCP Server

AI agents call list_installed_cores 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.

Why list_installed_cores needs a policy

This tool retrieves or enumerates data about Arduino cores already installed on the system with no side effects, modifications, deletions, or external operations. It is a read-only information retrieval function consistent with the Read category. Severity is low as the worst outcome is information disclosure about the development environment.

From the tool's definition Tool name 'list_installed_cores' indicates a listing/query operation that retrieves information about installed Arduino cores.

Questions about list_installed_cores

What does the list_installed_cores tool do? +

list_installed_cores. It is categorised as a Read tool in the Arduino MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_installed_cores? +

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

list_installed_cores is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_installed_cores? +

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.