get_kubernetes_resource
AI agents call get_kubernetes_resource to retrieve information from Lumino 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 designed to retrieve Kubernetes resource data (pods, services, deployments, etc.) for observability and debugging purposes. No evidence of write, delete, execute, or financial operations. Severity is medium because unauthorized access to Kubernetes resources could expose sensitive cluster configuration, secrets, or operational data.
From the tool's definition Tool name 'get_kubernetes_resource' indicates data retrieval. Description is empty, but the naming convention and context (SRE observability server with debugging tools) strongly suggest this fetches/queries Kubernetes resource information without…
Attacks that exploit this kind of access
get_kubernetes_resource. It is categorised as a Read tool in the Lumino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumino MCP Server MCP server in PolicyLayer and add a rule for get_kubernetes_resource: 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 Lumino MCP Server. Nothing to install.
get_kubernetes_resource 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 get_kubernetes_resource 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 get_kubernetes_resource. 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.
get_kubernetes_resource is provided by the Lumino MCP Server MCP server (lumino-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 →