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.
This record as markdown: /tools/denkopsai-mcp/get-container-logs.md
What get_container_logs does on Denkopsai
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
level | string | — | |
lines | integer | — | |
since | string | — | |
project_id | string | Yes |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_container_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_container_logs, this is the rule to start with:
get_container_logs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every get_container_logs call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
get_container_logs accepts 4 parameters: level, lines, since, project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for get_container_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 Denkopsai. Nothing to install.
get_container_logs 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_container_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.
Set action: deny in the PolicyLayer policy for get_container_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.
get_container_logs is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue