List all compute servers (blades and rack units) with optional filtering
AI agents call list_compute_servers to retrieve information from Intersight MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing server inventory information without modifying, deleting, or executing any actions. It is a straightforward read operation typical of infrastructure monitoring. The optional filtering does not change the read-only nature of the operation.
From the tool's definition Tool name and description indicate retrieval of server inventory data: 'List all compute servers (blades and rack units) with optional filtering'. This is a passive query operation with no modification capability.
Documented attack patterns abuse exactly the kind of access list_compute_servers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Intersight MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_compute_servers:
{
"version": "1",
"default": "deny",
"tools": {
"list_compute_servers": {}
}
}list_compute_servers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all compute servers (blades and rack units) with optional filtering. It is categorised as a Read tool in the Intersight MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Intersight MCP Server MCP server in PolicyLayer and add a rule for list_compute_servers: 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 Intersight MCP Server. Nothing to install.
list_compute_servers 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_compute_servers 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_compute_servers. 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_compute_servers is provided by the Intersight MCP Server MCP server (jim-coyne/intersight_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Intersight MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
198 Intersight MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.