AI controls, solved.

Provenant is the AI control plane built on guarantees.

An agent decides its own steps.

You can’t list every way it goes wrong.

✕

Detection

Catches the obvious, misses the novel.

✕

Blocklists

The list never ends. AI phrases each call differently.

✕

Allowlists

Too narrow for utility, or too open for safety.

Give every agent the right access at every step.
What each agent can see and do changes with its context.

One policy, wherever your agents run.

Apply it to any MCP server or in the agent harness. It shapes what the model sees at each step.

Access

The tools and data each agent is offered follow its context. Earlier results decide what’s next.

Isolation

Isolate context for any step in one line of policy, so each step sees only what it needs.

Guarantees

Read everything an agent can reach before you ship it. Prove what it can never do.

Evidence

Every decision signed and tied to the policy version that made it.

Your agents finish more, on fewer tokens.
The controls shape what they see.

From policy to proof.

MCP CLIENTany agentHARNESSyour agentPROVENANTone policyMCP SERVERSyours or third-partyAPISinternal servicesDATArecords and files
STAGE 1STAGE 2STAGE 3tools offered at each stagesearchreadread · field hiddenupdateclosesend(to,body)from an earlier tool
LIVE MODELyour agentPOLICYunder testEMULATED SYSTEMSnothing live touchedASSERTalways · send only after approvalASSERTat the end · the task is done
STAGE 1STAGE 2STAGE 3searchsearchsearchreadreadreadupdateupdateupdateclosecloseclosesendsendsendthe model is offered only the current stage’s tools
REPORTgenerated from the policysendRequires a person’s approval before it runs.readHides ssn, card_number anddate_of_birth from the model.send.toFilled from the record read earlier;the agent never chooses that value.SIGNED LOGwhat the agent did12:04:11 stage 1readallowedpolicy v3 · sig 9f2c…a7112:04:15 stage 2updateallowedpolicy v3 · sig 1a8f…03c12:04:22 stage 3sendapproved by a personpolicy v3 · sig 7be0…d42

For agents you don’t run, and agents you do.

Open your product to customer agents

Offer your tools over MCP with limits your customers can check.

  • Each customer’s agent sees only that customer’s data
  • Each agent is offered only what your policy allows
  • Provenant generates a plain report of everything each agent can reach

Connect agents to your production systems

Put agents on real systems without handing them the keys.

  • Sensitive fields never reach the model
  • Refunds and deletes over your limit wait for a person
  • After untrusted input, tools that send data out are gone

We tested agents under attack.

180 tasks on a public benchmark, each with a hijacking attempt hidden in the content the agent reads.

2.5×

more tasks completed than the same model on its own

39%

lower cost per completed task

0

actions taken that the policy ruled out

A small model under Provenant finished twice as many tasks as GPT-5.1 on its own, at one-ninth the cost per task.

Every published detection-based defense finished fewer tasks than no defense at all.

Bring us the workflow. Tell us what must never happen.

Pick one workflow that matters. We’ll write the policy with you and point a real agent at it.