List Rancher projects, optionally filtered by cluster.
AI agents call list_projects to retrieve information from Rancher 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 lists project information from Rancher without any side effects. It is a read-only query operation consistent with other list operations in the server (list_clusters, list_pods, list_deployments). The optional filtering parameter does not change its fundamental nature as a retrieval operation. Blast radius is minimal — exposure only enables information discovery about projects within Rancher.
From the tool's definition Tool name is 'list_projects' and description states 'List Rancher projects, optionally filtered by cluster' — a straightforward query operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List Rancher projects, optionally filtered by cluster. It is categorised as a Read tool in the Rancher MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rancher MCP Server MCP server in PolicyLayer and add a rule for list_projects: 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 Rancher MCP Server. Nothing to install.
list_projects 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_projects 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_projects. 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_projects is provided by the Rancher MCP Server MCP server (lokimcpuniverse/rancher-mcp-server). 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 →