Get detailed cost analysis for a specific cluster including
AI agents call get_cluster_analysis to retrieve information from Kubopt without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Kubernetes cluster cost information and returns analysis results. It performs read-only retrieval of cost metrics and analysis without creating, modifying, deleting, or executing any operations. The 'get_' prefix and 'analysis' function confirm data retrieval.
From the tool's definition Tool name is 'get_cluster_analysis' and description states 'Get detailed cost analysis for a specific cluster' — purely retrieves and queries cluster cost data with no side effects mentioned.
Documented attack patterns abuse exactly the kind of access get_cluster_analysis gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kubopt, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cluster_analysis:
{
"version": "1",
"default": "deny",
"tools": {
"get_cluster_analysis": {}
}
}get_cluster_analysis is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed cost analysis for a specific cluster including. It is categorised as a Read tool in the Kubopt MCP Server, which means it retrieves data without modifying state.
Register the Kubopt MCP server in PolicyLayer and add a rule for get_cluster_analysis: 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 Kubopt. Nothing to install.
get_cluster_analysis 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_cluster_analysis 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_cluster_analysis. 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_cluster_analysis is provided by the Kubopt MCP server (kubeopt/kubeopt). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kubopt, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Kubopt tools catalogued and risk-classified — across an index of 43,000+ MCP servers.