AI agents call node_capacity to retrieve information from Kubernetes Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Kubernetes node capacity information, which is a read-only query operation. No side effects, modifications, deletions, or external execution capabilities are implied. The confidence is 0.85 rather than higher only because the description is empty, but context from the server's declared read-only nature and sibling tools strongly indicates this is a simple information retrieval tool.
From the tool's definition Tool name 'node_capacity' combined with server description stating 'read-only MCP server' and sibling tools like 'list_nodes', 'get_namespaces', 'get_resource_yaml' which are all query/retrieval operations.
Documented attack patterns abuse exactly the kind of access node_capacity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kubernetes Monitor, and nothing reaches the server without passing your rules. This is the rule we recommend for node_capacity:
{
"version": "1",
"default": "deny",
"tools": {
"node_capacity": {}
}
}node_capacity 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.
node_capacity. It is categorised as a Read tool in the Kubernetes Monitor MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes Monitor MCP server in PolicyLayer and add a rule for node_capacity: 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 Monitor. Nothing to install.
node_capacity 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 node_capacity 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 node_capacity. 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.
node_capacity is provided by the Kubernetes Monitor MCP server (vlttnv/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kubernetes Monitor, 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.
12 Kubernetes Monitor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.