get_k8s_logs

Gets logs from a Kubernetes container in a pod. This is similar to running kubectl logs.

SERVERMcp SOURCEhttps://container.googleapis.com/mcp

Low RISK CLASS

Category Read

Parameters 102 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-container-mcp/get-k8s-logs.md

WHAT IT DOES

What get_k8s_logs does on Mcp

AI agents call get_k8s_logs to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`name`	string	Yes	Required. The name of the resource to retrieve logs from. This can be a pod name (e.g. "my-pod") or a type/name (e.g. "deployment/my-deployment"). If a type is
`tail`	string	—	Optional. The number of lines from the end of the logs to show.
`since`	string	—	Optional. Retrieve logs since this duration ago (e.g. "1h", "10m").
`parent`	string	Yes	Required. The cluster to retrieve logs from. Format: projects/{project}/locations/{location}/clusters/{cluster}
`previous`	boolean	—	Optional. If true, retrieve logs from the previous instantiation of the container.
`container`	string	—	Optional. The name of the container to retrieve logs from. If not specified, logs from the first container are returned.
`namespace`	string	—	Optional. The namespace of the resource. If not specified, "default" is used.
`sinceTime`	string	—	Optional. Retrieve logs since this time (RFC3339). e.g. "2024-08-30T06:00:00Z".
`timestamps`	boolean	—	Optional. If true, include timestamps in the log output.
`allContainers`	boolean	—	Optional. If true, retrieve logs from all containers in the pod.

Parameters from the server's own tool schema.

RISK

Why get_k8s_logs is rated Low

This tool retrieves existing log data from Kubernetes containers, which is a pure read operation with no side effects. It does not create, modify, delete, or execute any code. The server description confirms it 'Provides read access' to Kubernetes resources. The blast radius of misuse is minimal—an agent could read sensitive logs but cannot alter cluster state or infrastructure.

From the tool's definition Tool description states 'Gets logs from a Kubernetes container in a pod' and explicitly compares it to `kubectl logs`, which is a read-only operation that retrieves log output without modifying any resources.

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_k8s_logs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_k8s_logs, this is the rule to start with:

get_k8s_logs Allowed

get_k8s_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_k8s_logs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every get_k8s_logs call is checked against it from then on.

FAQ

Questions about get_k8s_logs

What does the get_k8s_logs tool do? +

Gets logs from a Kubernetes container in a pod. This is similar to running kubectl logs. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_k8s_logs accept? +

get_k8s_logs accepts 10 parameters: name, tail, since, parent, previous, container, namespace, sinceTime, timestamps, allContainers. Required: name, parent. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_k8s_logs? +

Register the MCP server in PolicyLayer and add a rule for get_k8s_logs: 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 Mcp. Nothing to install.

What risk level is get_k8s_logs? +

get_k8s_logs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_k8s_logs? +

Yes. Add a rate_limit block to the get_k8s_logs 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.

How do I block get_k8s_logs completely? +

Set action: deny in the PolicyLayer policy for get_k8s_logs. 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 get_k8s_logs? +

get_k8s_logs is provided by the MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 23 tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →