list_k8s_resources
AI agents call list_k8s_resources to retrieve information from GreenNode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to list or retrieve Kubernetes resources from a cluster without modifying them. Listing resources is a read-only operation with minimal blast radius—an agent using this tool would only gain visibility into existing infrastructure state. The empty description reduces confidence slightly, but the semantic meaning of 'list' in infrastructure contexts is unambiguously a read operation.
From the tool's definition Tool name 'list_k8s_resources' indicates a listing/querying operation. The 'list' verb is a common pattern for retrieval operations without side effects.
Attacks that exploit this kind of access
list_k8s_resources. It is categorised as a Read tool in the GreenNode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for list_k8s_resources: 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 GreenNode MCP Server. Nothing to install.
list_k8s_resources 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_k8s_resources 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_k8s_resources. 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_k8s_resources is provided by the GreenNode MCP Server MCP server (vngcloud/greennode-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 →