Compares pod CPU/Memory usage against limits to check for threshold violations
AI agents call check-resources to retrieve information from K8s Doctor MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic queries on Kubernetes resource metrics (CPU, Memory) and compares them against configured limits. It reads pod resource data and performs analysis, which is characteristic of Read category tools. There are no side effects, no code execution, no data modification, and no destructive operations.
From the tool's definition Tool description states it 'Compares pod CPU/Memory usage against limits to check for threshold violations' — a purely observational operation that retrieves and analyzes existing resource metrics without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Compares pod CPU/Memory usage against limits to check for threshold violations. It is categorised as a Read tool in the K8s Doctor MCP MCP Server, which means it retrieves data without modifying state.
Register the K8s Doctor MCP server in PolicyLayer and add a rule for check-resources: 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 Doctor MCP. Nothing to install.
check-resources 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 check-resources 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 check-resources. 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.
check-resources is provided by the K8s Doctor MCP server (ongjin/k8s-doctor-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 →