This website counts page views with Cloudflare Web Analytics, which sets no cookies and stores nothing on your device. If you choose Allow, embedded content such as Spotify podcast players also sets optional cookies. Choose Deny to turn off both. Cookie Notice
Hold risky agent actions for approval. Before they run.
Runtime checks each agent action before it runs and holds the ones that can't be undone, from a recruiter's upload of candidate resumes to terraform destroy, for a person to approve.
Upload the resumes in Candidates/Senior designer to hirescreen.example so they can rank them
⏺Upload files to hirescreen.example
Waiting for approval · Signals Corps Runtime
Rule
Candidate files to an unapproved site
Severity
High
Decision
Ask for approval
Approver
HR operations lead
⏺I haven't uploaded anything yet. hirescreen.example isn't on your company's approved list for candidate files, so an HR operations lead needs to approve it. I'll upload the resumes once they do.
The problem
One action from an agent can't always be undone.
Agents act with the access of the person using them, from a recruiter's candidate folders to an engineer's production systems.
A recruiter can ask the Claude desktop app to upload a folder of candidate resumes to an outside screening site, and once the files leave, nobody can call them back. A sales rep can ask the ChatGPT desktop app to email a customer spreadsheet to a personal address. In engineering, an agent asked to clean up a branch can run git push --force to main. One asked to reset a test environment can run terraform destroy in the wrong workspace, or send DROP TABLE through psql to a live database. People often approve each step in a hurry, or turn the agent's own prompts off.
Research and public incidents show agents already take actions nobody intended.
80%
of IT professionals surveyed say their organization's AI agents have taken unintended actions, such as accessing systems or data they shouldn't.
Dimensional Research survey for SailPoint of 353 IT professionals responsible for AI, security, and identity.
Agents doing things nobody asked for is already common, so the riskiest actions need a check before they run.
Risky actions wait for a person while routine work carries on.
Approvals
Uploads and destructive commands wait for approval
Set a rule to ask for approval, and a recruiter's upload of candidate resumes to a site outside your approved list, or terraform destroy, pauses until an approver says yes or no in Control Plane. The agent waits, and the person using it sees why.
Blocking
Some actions never run
Block what should never come from an agent, such as an email of a customer spreadsheet to a personal address, rm -rf on a project root, or a force push to a protected branch. The agent reports that the action was blocked and which rule matched.
Databases
Database changes get a check
Runtime checks commands sent through a database CLI, so DROP TABLE in psql or mysql can ask for approval or be blocked, while SELECT queries run as usual.
Speed
Everything else runs as usual
Runtime decides on the device with local rules, with no model or network call in the decision, so npm test and git commit go through untouched.
How it works
Watch first. Add approvals where the risk justifies them.
You see what each rule would stop before it stops anything.
01 · RuntimeWatch in log mode
Push one package through your device management tool, such as Jamf, Iru, or Intune, and approve each device's enrollment code in Control Plane. The decision log shows which commands your rules would have stopped, while nothing is stopped.
02 · RuntimeAsk for approval on the riskiest actions
Start with uploads of candidate and customer files to unapproved sites, terraform destroy, DROP TABLE, and force pushes to protected branches. Requests go to IT & Security teams, or the approvers you choose, in Control Plane.
03 · RuntimeBlock what should never run
Switch the rules you never want to approve, such as sends of customer data to personal addresses or rm -rf on a project root, from approval to block.
Runtime / Approval requestIllustrative data
Waiting request · expires in min
terraform destroy -auto-approve
Workspace staging-eu
Destroy cloud infrastructure
Severity high · ask for approval
Claude Code
Platform team · 1 device
Platform leads
can approve · developer waiting seconds
DenyApprove
In Control Plane
Approve or deny while the agent waits.
Each request shows the rule that matched and the agent that asked.
Approval requests waiting, with who can approve them
Allowed, approval, or blocked, with the matched rule on each action in the decision log
Coverage per agent on each device: whether Runtime can observe, ask for approval, or block
Case study
How many approvals to expect.
A 300-person fintech gives 140 engineers Claude Code.
74 of 300 devices already ran Claude Code before anyone approved it
212 components found on day one, 3 blocked in the first week
About 40 approval requests a week, out of roughly 200,000 checked actions
What it costs
Priced per device. Always predictable.
Runtime is priced per device, with free devices on every plan. Your bill depends on how many devices you cover, so heavier agent use doesn't change it, and finance can plan ahead.
How do we stop an agent sending files out or deleting our data?
Runtime checks each upload, send, and shell command before it runs. A rule can ask for approval in Control Plane while the agent waits, for example on an upload of candidate files to an unapproved site or on terraform destroy, or block the action.
Who approves, and what happens while they decide?
IT & Security teams, or the approvers you choose, approve or deny the request in Control Plane. The request shows the action, the rule, the agent, and the device, so they decide with the full picture. The action waits, and the person using the agent sees which rule asked for approval.
Won't approvals slow our teams down?
Your teams keep their pace, because only the actions you choose ask for approval. In the case study above, that was about 40 a week out of roughly 200,000 checked actions. Start in log mode to see how often a rule would fire before you turn it on.
Which agents does it work with?
The agents your teams already use, including the Claude desktop app, the ChatGPT desktop app, Claude Code, Codex, Cursor, Windsurf, and agents built on other frameworks.
Reduce agent risk without slowing your teams down.
Start reducing agent risk before general release by checking agent components, controlling agent actions, and hunting through your AI security logs. Signals Corps Control Plane opens to early sign ups in the next few weeks, so join the waitlist with your company email.