New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

docker_logs

Retrieve logs from a Docker container.

SERVERTerminal Guardian SOURCE7majesty-m/terminal-guardian-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/7majesty-m-terminal-guardian-mcp/docker-logs.md

What docker_logs does on Terminal Guardian

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

Why docker_logs is rated Low

This tool retrieves log data from Docker containers, which is a non-destructive query operation. It has no side effects on the container, system, or data. While logs may contain sensitive information, the tool itself only reads and returns existing data. The severity is low because exposure of this tool allows information gathering only, not code execution or data modification.

From the tool's definition Tool name 'docker_logs' and description 'Retrieve logs from a Docker container' indicate a read-only operation that queries existing log data without modification or execution.

Questions about docker_logs

What does the docker_logs tool do? +

Retrieve logs from a Docker container. It is categorised as a Read tool in the Terminal Guardian MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docker_logs? +

Register the Terminal Guardian MCP server in PolicyLayer and add a rule for docker_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 Terminal Guardian. Nothing to install.

What risk level is docker_logs? +

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

Can I rate-limit docker_logs? +

Yes. Add a rate_limit block to the docker_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 docker_logs completely? +

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

docker_logs is provided by the Terminal Guardian MCP server (7majesty-m/terminal-guardian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Terminal Guardian, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Terminal Guardian's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.