This document defines the security boundaries, authorization tiers, and permission constraints for AI agents interacting with this project.
Autonomous AI agents and subagents operate under strict read-preferred, bounded-write constraints:
docker compose, docker run) or allowlisted inspection commands.| Tier | Scope | Permissions Granted | Authorization Requirement |
|---|---|---|---|
| Tier 1 (Read-Only) | File inspection, git log, OTel telemetry, metrics, MCP tool queries | Unrestricted within project bounds | Fully Autonomous |
| Tier 2 (Safe Non-Destructive) | Test execution, container startup (docker compose up), local build |
Container execution permitted | Autonomous with Audit Log |
| Tier 3 (Modifying Source) | Code edits, test creation, configuration updates | Scoped to project files | Bounded Autonomy (Git-tracked) |
| Tier 4 (Privileged / Destructive) | Database schema dropping, hard resets, force pushing | STRICTLY BLOCKED | Requires Explicit Human Approval |
docker compose ps / docker compose logs / docker compose up -d / docker compose downdocker compose run --rm <service> <test_cmd>git status / git diff / git logcurl -s http://localhost:<PORT>/healthpython3 mcp-server/server.pyagent-hooks/pre-tool-guardrail.sh)rm -rf / or rm -rf ~DROP DATABASE, TRUNCATE TABLE, unconstrained DELETEgit push --force to protected branches (main, master)All Model Context Protocol tools declared in mcp-server/mcp.json operate with read-only inspection scopes:
inspect_project_health: Reads container status via Docker Compose; does not stop or mutate containers.inspect_openapi_contract: Reads contracts/openapi.yaml; does not write or modify contracts.Every agent action and hook outcome is captured in agent-hooks/audit.log for post-run compliance review.