exec_in_pod
Execute a command in a Kubernetes pod or container and return the output. Command must be an array of strings where the first element is the executable and remaining elements are arguments. This executes directly without shell interpretation for security.
Part of the Kubernetes MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents invoke exec_in_pod to trigger processes or run actions in Kubernetes. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
WHY ENFORCE A POLICY ON EXEC_IN_POD
exec_in_pod can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
exec_in_pod:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Kubernetes policy for all 22 tools.
DETAILS
MORE KUBERNETES TOOLS
kubectl_generic Execute cleanup Other explain_resource Other install_helm_chart Other kubectl_apply Other kubectl_context Other kubectl_create Other kubectl_delete Other SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the exec_in_pod tool do?
Execute a command in a Kubernetes pod or container and return the output. Command must be an array of strings where the first element is the executable and remaining elements are arguments. This executes directly without shell interpretation for security.. It is categorised as a Execute tool in the Kubernetes MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
How do I enforce a policy on exec_in_pod?
Add a rule in your Intercept YAML policy under the tools section for exec_in_pod. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kubernetes MCP server.
What risk level is exec_in_pod?
exec_in_pod is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit exec_in_pod?
Yes. Add a rate_limit block to the exec_in_pod rule in your Intercept 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.
How do I block exec_in_pod completely?
Set action: deny in the Intercept policy for exec_in_pod. 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.
What MCP server provides exec_in_pod?
exec_in_pod is provided by the Kubernetes MCP server (). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON KUBERNETES
Open source. One binary. Zero dependencies.