Get portfolio-level cost summary across all clusters
AI agents call get_cost_summary 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 retrieves and queries cost summary information without any side effects. It falls squarely under the Read category as it provides visibility into existing Kubernetes cluster costs without modifying infrastructure, executing operations, or making financial changes. The blast radius of misuse is minimal—an agent could only gain unauthorized visibility into cost data.
From the tool's definition Tool name 'get_cost_summary' and description 'Get portfolio-level cost summary across all clusters' indicate data retrieval. No modification, deletion, code execution, or financial transactions occur—only querying cost analysis data.
Documented attack patterns abuse exactly the kind of access get_cost_summary 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_cost_summary:
{
"version": "1",
"default": "deny",
"tools": {
"get_cost_summary": {}
}
}get_cost_summary 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 portfolio-level cost summary across all clusters. 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_cost_summary: 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_cost_summary 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_cost_summary 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_cost_summary. 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_cost_summary 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.