AI agents call get_deployment to retrieve information from K8s without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Kubernetes deployment metadata and status without modifying, deleting, or executing operations. It is a read-only inspection tool that gathers information about existing deployments. No data is created, modified, deleted, or executed. The severity is low as misuse would only expose information already accessible to a user with view permissions on the cluster.
From the tool's definition Tool name 'get_deployment' and description 'Get detailed information about a deployment' indicate a retrieval operation with no side effects. The verb 'Get' and context of 'detailed information' align with query/inspection functionality.
Attacks that exploit this kind of access
Get detailed information about a deployment. It is categorised as a Read tool in the K8s MCP Server, which means it retrieves data without modifying state.
Register the K8s MCP server in PolicyLayer and add a rule for get_deployment: 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 K8s. Nothing to install.
get_deployment 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_deployment 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_deployment. 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_deployment is provided by the K8s MCP server (jingyanjiang/k8s-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 →