surehand

Every action clears the rules before it runs.

Not a review afterwards.

Each action is checked against the signed rules as it happens. Allowed actions go ahead.

Everything else stops before it reaches your systems, and the stop is recorded.

One worked example runs through these pages. The screens are simulated, the figures are invented, and each one says so.

/ fig. 01Three actions pass, the payment is held. The rule that fired, expanded. Simulated.
[ access ]

The agent gets the keys the job needs. Nothing else.

Every call the agent makes to one of your systems passes through Gatehouse. It holds only the credentials the job needs, for as long as it needs them.

Without a credential, a system is out of reach. Access is least privilege, and the access itself is logged: who read what, for which run, under which scope.

/ fig. 02Every call passes through Gatehouse. The payment stops before the bank portal. Simulated.
[ injection ]

A prompt injection tries to send mail.

A document the agent reads carries a hidden instruction: send the supplier list to an outside address.

The rules give the agent no scope for outbound mail, so it holds no mail credential. Nothing is sent. The attempt is refused and saved to the record.

/ fig. 03An injected instruction meets the rules. Nothing leaves. Composite scenario. Simulated.
[ refusals ]

Refusals are part of the record.

A stop that nobody can see is a stop nobody can check. Each refusal is written to the record with the action attempted, the rule that refused it and the time.

Your reviewers read refusals the way they read everything else: from the record, without asking us.

[ questions ]

What reviewers ask about this part.

Not here? Write to support@surehand.io. A person replies, usually inside two business days.

Book a walkthrough
What if a prompt injection tells the agent to do something else?

The agent can only reach what the rules name, with credentials held for the job. An instruction to send mail it has no scope for goes nowhere. The attempt is refused and saved to the record.

Are refusals recorded?

Yes. A refused action goes into the record with the rule that refused it and the time, the same as an action that ran.

[ all seven parts ]

Everything between the agent and your systems.

Start here

Bring us the queue nobody wants.

A teardown measures one process, and you keep the document. A walkthrough is 30 minutes on Gatehouse, no slides. We bring the rules and the sealed record of one held payment. You bring one live process and your reviewers' questions.

support@surehand.io