# get_container_logs

Read recent container logs for a DenkOps project (for debugging a failing deploy). Optional since (e.g. 15m, 2h, 3d, or an ISO timestamp) and level (a token matched in the log line, e.g. error) filter the persisted log store.

Agent View of the PolicyLayer registry record for `get_container_logs`. HTML page: https://policylayer.com/tools/denkopsai-mcp/get-container-logs

## Facts

- Tool: `get_container_logs`
- Server: Denkopsai (`@denkopsai/mcp`) — https://policylayer.com/tools/denkopsai-mcp.md
- Install: `npx -y @denkopsai/mcp`
- Homepage: https://www.npmjs.com/package/@denkopsai/mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 4 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `level` | string | no |  |
| `lines` | integer | no |  |
| `since` | string | no |  |
| `project_id` | string | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_container_logs",
    "arguments": {
      "project_id": "<project_id>"
    }
  }
}
```

## Why get_container_logs is rated Low

This tool retrieves and queries log data for a DenkOps project with optional filtering. It has no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal: an attacker could read logs to gather information about deployments, but cannot cause direct harm through this tool alone. This is a classic Read operation.

From the tool's own definition: "Tool name and description explicitly state 'Read recent container logs' with filtering options (since, level). The description clarifies this is for 'debugging a failing deploy' and retrieves log data without modification or deletion."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Denkopsai:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_container_logs": {}
  }
}
```

## Other tools on Denkopsai (27)

- `delete_project` — Destructive — https://policylayer.com/tools/denkopsai-mcp/delete-project.md
- `remove_domain` — Destructive — https://policylayer.com/tools/denkopsai-mcp/remove-domain.md
- `revoke_connection` — Destructive — https://policylayer.com/tools/denkopsai-mcp/revoke-connection.md
- `unset_env` — Destructive — https://policylayer.com/tools/denkopsai-mcp/unset-env.md
- `deploy` — Execute — https://policylayer.com/tools/denkopsai-mcp/deploy.md
- `login` — Execute — https://policylayer.com/tools/denkopsai-mcp/login.md
- `redeploy` — Execute — https://policylayer.com/tools/denkopsai-mcp/redeploy.md
- `start_project` — Execute — https://policylayer.com/tools/denkopsai-mcp/start-project.md
- `stop_project` — Execute — https://policylayer.com/tools/denkopsai-mcp/stop-project.md
- `get_denkops_guide` — Read — https://policylayer.com/tools/denkopsai-mcp/get-denkops-guide.md
- `get_egress_policy` — Read — https://policylayer.com/tools/denkopsai-mcp/get-egress-policy.md
- `get_metrics` — Read — https://policylayer.com/tools/denkopsai-mcp/get-metrics.md
- `get_public_paths` — Read — https://policylayer.com/tools/denkopsai-mcp/get-public-paths.md
- `get_status` — Read — https://policylayer.com/tools/denkopsai-mcp/get-status.md
- `get_trace` — Read — https://policylayer.com/tools/denkopsai-mcp/get-trace.md
- `list_connections` — Read — https://policylayer.com/tools/denkopsai-mcp/list-connections.md
- `list_domains` — Read — https://policylayer.com/tools/denkopsai-mcp/list-domains.md
- `list_env` — Read — https://policylayer.com/tools/denkopsai-mcp/list-env.md
- `list_projects` — Read — https://policylayer.com/tools/denkopsai-mcp/list-projects.md
- `list_traces` — Read — https://policylayer.com/tools/denkopsai-mcp/list-traces.md
- `rollback` — Read — https://policylayer.com/tools/denkopsai-mcp/rollback.md
- `verify_domain` — Read — https://policylayer.com/tools/denkopsai-mcp/verify-domain.md
- `add_domain` — Write — https://policylayer.com/tools/denkopsai-mcp/add-domain.md
- `create_connection` — Write — https://policylayer.com/tools/denkopsai-mcp/create-connection.md
- `set_egress_policy` — Write — https://policylayer.com/tools/denkopsai-mcp/set-egress-policy.md
- `set_env` — Write — https://policylayer.com/tools/denkopsai-mcp/set-env.md
- `set_public_paths` — Write — https://policylayer.com/tools/denkopsai-mcp/set-public-paths.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=denkopsai-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/denkopsai-mcp