Get all cronjobs
AI agents call get_cronjobs 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 queries and retrieves information about Kubernetes cronjobs without creating, modifying, deleting, or executing any resources. It is a pure read operation with no side effects. Severity is low because exposure of cronjob metadata does not directly enable harmful actions, though it could inform reconnaissance in a broader attack.
From the tool's definition Tool name is 'get_cronjobs' and description states 'Get all cronjobs' — a retrieval operation with no modification or execution of resources.
Attacks that exploit this kind of access
Get all cronjobs. 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 get_cronjobs: 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.
get_cronjobs 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_cronjobs 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_cronjobs. 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_cronjobs is provided by the Kubernetes MCP Server MCP server (surukanti/k8s-mcp-server). 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 →