List catalog applications installed in a Rancher cluster.
AI agents call list_catalog_apps 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 queries and returns information about installed catalog applications in a Rancher cluster. It performs no side effects, creates no resources, modifies no state, and executes no commands. It is a straightforward read/list operation, consistent with other benign listing tools on this server (list_clusters, list_pods, list_deployments, etc.).
From the tool's definition Tool name 'list_catalog_apps' and description 'List catalog applications installed in a Rancher cluster' indicate a retrieval operation with no modification, deletion, or code execution.
Attacks that exploit this kind of access
List catalog applications installed in a Rancher 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_catalog_apps: 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_catalog_apps 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_catalog_apps 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_catalog_apps. 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_catalog_apps 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 →