Security Modes
profClaw has five security levels for tool execution:| Mode | Description |
|---|---|
deny | No tools allowed |
sandbox | Only read-only tools |
allowlist | Only explicitly allowed tools |
ask | Prompt for approval before sensitive operations |
full | All tools pre-approved (agentic mode default) |
GET /api/security/policy
Get the current security policy configuration.200
PUT /api/security/policy
Update the security policy.GET /api/security/audit
Retrieve the audit log of agent tool executions.200
limit, offset, tool, userId, conversationId, from, to
GET /api/security/audit/:id
Get a single audit entry with full argument and result details.Tool Approval Queue
WhensecurityMode is ask, tool calls requiring approval are queued until a user decision is made.
GET /api/security/approvals
List pending tool approvals.POST /api/security/approvals/:id
Submit an approval decision.allow-once | allow-always | deny
allow-always adds the tool to the session allowlist so subsequent calls proceed without prompting.
Guard Configuration
Guards are pre-execution checks that block unsafe tool calls regardless of security mode:| Guard | Blocks |
|---|---|
path-traversal | Paths containing ../ or absolute paths outside workdir |
shell-injection | Shell metacharacters in command arguments |
secret-exfiltration | Reads of .env, credential files |
rate-limit | Tool calls exceeding configured rate |
Related
- Security Overview - Security modes, guards, and audit architecture
- profclaw security - Manage security policies from the CLI
- profclaw audit - View the audit log from the CLI
- Tools Overview - Tool security levels and execution pipeline