How it works

One gateway between your agents and everything they touch.

Clawvisor sits in the request path between your agent and the services it reaches for. Every request runs through policy first: purpose verified, risk scored, credentials injected, calls logged, before it touches your accounts.

The request path

Point your agent at Clawvisor. Everything else falls out of that.

Your agent

Claude Code

Clawvisor

verify · inject · log

Your services

Gmail

The lifecycle of a single task

01

The agent declares a task

Instead of asking for tools one call at a time, the agent states a task: a purpose plus the tools it expects to need. Clawvisor sits in the request path, so this happens with no SDK and no agent rewrite.

02

Clawvisor scores the blast radius

Every task is assessed for how much damage it could do if it went wrong: reversibility, scope, and the sensitivity of the tools requested. The result is a low / medium / high risk rating on the request.

03

The gateway decides: pass or hold

Requests that match the approved task scope and are low-risk flow straight through. Anything outside that scope, or on your blocked list of services and actions, pauses and waits for a named human to approve or deny.

04

Scoped execution, then revocation

On approval, the gateway swaps vaulted credentials in at call time and grants exactly the scopes the task declared, nothing adjacent. Every call is logged and tied to the task. When the task ends, the grant is revoked.

Approval required

Triage the failing CI check on billing-api and file an issue.

dev-agentexpires when task completes
Tools requested3

  • github · get_pr

    repo: billing-api

    read

  • github · search_code

    repo: billing-api

    read

  • github · create_issue

    repo: billing-api

    write
medium risk

Approve the task, and the power-ups come with it.

Requests must match the task

Purpose verification

You approve a task, not a standing permission. Every request the agent makes is checked against the purpose you approved — a calendar read for your morning briefing goes through, an expense audit across all history does not.

Every action on the record

Audit trail

Every request, every purpose declaration, every decision, every credential injection. A complete record of what your agent asked for and what Clawvisor allowed.

The agent never sees your keys

Credential injection

Your API keys and OAuth tokens live in an encrypted vault. Clawvisor injects credentials server-side and returns sanitized results, so a leaked prompt or transcript can't leak a token.

Scored before it runs

Risk assessment

Every request is scored for risk before execution. Clawvisor flags anomalous parameters, unusual access patterns, scope creep, and prompt-injection attempts hiding in tool arguments.

Let your agents act. Safely.

Connect your accounts and put a gatekeeper in front of your agents in minutes. Free to start, no credit card.

Get started freeRead the docs