# compose-logs

Retrieves Docker Compose service logs as structured entries.

Agent View of the PolicyLayer registry record for `compose-logs`. HTML page: https://policylayer.com/tools/io-github-dave-london-pare-search/compose-logs

## Facts

- Tool: `compose-logs`
- Server: Search (`Dave-London/Pare`) — https://policylayer.com/tools/io-github-dave-london-pare-search.md
- Homepage: https://github.com/Dave-London/Pare
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compose-logs",
    "arguments": {}
  }
}
```

## Why compose-logs is rated Low

This tool retrieves log information from Docker Compose services, which is a read operation with no side effects. Logs are informational outputs that cannot be modified by reading them. The blast radius is minimal—an AI agent misusing this tool would only access logs it's authorized to see, without capability to alter infrastructure or trigger destructive actions.

From the tool's own definition: "Tool name 'compose-logs' and description 'Retrieves Docker Compose service logs as structured entries' indicate a read-only operation that queries existing log data without modifying, deleting, or executing commands."

## Use case

AI agents call compose-logs to retrieve information from Search 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 Search:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compose-logs": {}
  }
}
```

## Other tools on Search (201)

- `branch` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/branch.md
- `clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/clean.md
- `package-clean` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/package-clean.md
- `remove` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/remove.md
- `reset` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/reset.md
- `secret-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/secret-delete.md
- `stash` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/stash.md
- `tag` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/tag.md
- `variable-delete` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/variable-delete.md
- `workspace` — Destructive — https://policylayer.com/tools/io-github-dave-london-pare-search/workspace.md
- `add` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/add.md
- `add-package` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/add-package.md
- `ansible-galaxy` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/ansible-galaxy.md
- `ansible-playbook` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/ansible-playbook.md
- `api` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/api.md
- `apply` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/apply.md
- `audit` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/audit.md
- `bazel` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/bazel.md
- `biome-check` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/biome-check.md
- `bisect` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/bisect.md
- `black` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/black.md
- `build` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/build.md
- `bundle-exec` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/bundle-exec.md
- `bundle-install` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/bundle-install.md
- `check` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/check.md
- `checkout` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/checkout.md
- `cherry-pick` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/cherry-pick.md
- `clippy` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/clippy.md
- `cmake` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/cmake.md
- `compose-build` — Execute — https://policylayer.com/tools/io-github-dave-london-pare-search/compose-build.md
- …and 171 more: https://policylayer.com/tools/io-github-dave-london-pare-search.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=io-github-dave-london-pare-search · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-dave-london-pare-search