API and tool actions
Check requests against your rules before the connected application acts.
Computer-use governance · Generally available
Keep control when agents work through a screen
The agent clicking through a supplier portal never imported anyone's SDK. VeriProof puts the same policy check, the same reviewer, and the screen that explains the moment behind actions that happen through a browser.
One decision history across tools and screens
A workflow can start with an API call and finish in a browser. When the two halves live in different tools, nobody can follow the business action from one end to the other. Here they share one decision history.
Browser actions
An agent may work through a screen. Its actions still need policy checks and evidence.
Hybrid workflows
Follow API and browser steps together, even when the workflow moves between them.
- Policy results linked to the proposed action
- Human review with the decision context
- Key screen evidence and recorded outcomes
- Evidence exports with file checks and verification details
Computer-use MCP tools are generally available.
Check the action before the application commits
The check happens before the click commits. If policy says a person has to decide, the action waits, and their answer comes back into the workflow with the rest of the record.
API and toolsBrowserWorkflow and code
- Requested action→
- Policy check→
- Review if needed→
- Application applies decision→
- Reported outcome→
- Evidence pack
An execution service confirms the outcome with the system that carried out the action, so the record does not have to rely on the agent's own account of what it did.
See the screens that explain the decision
One screen usually explains the decision. Capture the moments your policy names and skip the rest, so reviewers get the context without a session recording.
Keep the relevant moment
What was on screen when the agent acted? Keep exactly the moments your policy calls for, including the state of a workflow that was interrupted partway through.
Follow the action
Move from a policy result to the screen behind it. Flow View keeps captures with the steps they explain.
Share the supporting evidence
Give reviewers the permitted captures alongside decision evidence, with masking status included in the export.
Give reviewers more than the agent's account
Keep approval tied to the request
A review belongs to a specific action. Current-state checks help prevent an approval from being reused for changed or outdated work.
Confirm what happened
Key screens provide visual context. A connected execution service adds independent action evidence, giving reviewers another source alongside the agent's report.
Questions about computer-use governance
Yes. VeriProof's MCP computer-use tools support policy checks, human review, and key screen evidence for connected browser workflows.
Your application does. VeriProof checks the action, brings in a reviewer when policy calls for one, and keeps the decision, the review, and the screen evidence together afterward.
This capability uses selected screen captures. Your capture policy determines which moments to retain, keeping the evidence focused on relevant actions.
Put your rules behind the next click
Choose a browser workflow. See where VeriProof can check an action, bring in a reviewer, and preserve the screen evidence.