Recent deployment history
AI agents call deployments.listRecentChanges to retrieve information from Kubernetes 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 displays historical information about recent deployment changes in Kubernetes. It performs no modifications to cluster state, executes no commands, and has no destructive or financial implications. The read-only nature of accessing deployment history poses minimal risk—an agent cannot cause harm by querying change history.
From the tool's definition Tool name 'listRecentChanges' and description 'Recent deployment history' indicate a query/retrieval operation. The verb 'list' combined with 'history' (a read-only view of past events) confirms no modification or execution occurs.
Attacks that exploit this kind of access
Recent deployment history. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for deployments.listRecentChanges: 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 Kubernetes MCP Server. Nothing to install.
deployments.listRecentChanges 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 deployments.listRecentChanges 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 deployments.listRecentChanges. 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.
deployments.listRecentChanges is provided by the Kubernetes MCP Server MCP server (kishanrao92/infra-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 →