Before your AI acts, it asks what is allowed
The policy layer for AI agents and AI assistants. One MCP server and one REST API that return your current approved policy, word for word, and take exception requests to the people who approve them.
Connects to
- ClaudeMCP
- ChatGPTMCP
- Other MCP clientsMCP
- Your own agentsREST
Book me a hotel in Oslo on Tuesday, close to the office.
[{ "name": "Harbour Hotel", "walk": "2 min", "price": "2,400 kr" },
{ "name": "Station Hotel", "walk": "9 min", "price": "1,850 kr" }]{ "passages": [{
"policy": "Travel policy", "version": 3, "heading": "4. Hotels",
"text": "Hotel stays are covered up to 2,000 kr a night. A higher rate needs approval before booking."
}],
"not_covered": false }Harbour Hotel is closest, but at 2,400 kr it is over your limit of 2,000 kr a nightTravel policy · v3 · section 4. Station Hotel at 1,850 kr is within it. Book that one, or file an exception request for the Harbour?
I need the Harbour. Yes, file it please.
{ "reference": "KTR482", "status": "pending" }Filed, with the ID KTR482. An administrator decides, and you get the answer by email. I have not booked anything yet.
Every AI tool keeps its own copy of your policies
Project folders, custom instructions, rules in code, shared skills. Each one was right the day it was made.
"How long may we keep customer logs?"
The policy says 30 days, in version 3. No tool has it.
"How long may we keep customer logs?"
Every tool gets section 2 of version 3, word for word.
One connector for your people. One key for each agent.
An administrator chooses which policies each one can read. Nobody signs in.
Name Policy Confirm
URL from your administrator
Sign-in none
Tools ask_what_is_allowed
read_policy
request_exception
get_exception_status# In the agent's instructions
If you are unsure whether something is allowed, ask Policy Confirm.
POST /v1/ask
Authorization: Bearer <agent key>
{ "question": "May I deploy a hotfix during the change freeze?" }Any question an agent has. Three possible answers.
Policy text with its source, and no verdict. No model writes an answer on our side, so a question costs a search.
"passages": [{
"policy": "Secure development",
"version": 2,
"heading": "5. Licences",
"page": 4,
"text": "Copyleft licences need approval from security..."
}]The AI reads it and concludes.
"passages": [],
"searched": ["Data handling", "Change management"],
"not_covered": trueNot permission. The AI asks a person.
"unavailable": [{
"policy": "Access control",
"reason": "being_indexed"
}]Listed apart, never counted as not covered.
When the policy says no, the agent asks the people who approve
Today that question never reaches them. Now the agent files the request, waits, and carries on when the decision arrives.
The agent meets a rule it cannot pass
It stops. The task fails and someone finds out later.
The developer decides. An override in the code, written by whoever built the agent.
It goes ahead. Nobody who approves ever saw the question.
The people who approve exceptions are not in the loop.
agent run: deploy a hotfix during the change freeze
The pause
The policy requires approval. The agent files a request with the people who approve.
request_exceptionThe decision
An administrator decides in Policy Confirm. The agent is told by a signed webhook.
request changedPOST https://your-app.example/hooks/policy-confirm
{ "event": "exception_request.changed", "reference": "MHD207" }
GET /v1/exception-requests/MHD207 # "status": "approved"No tool lets an AI approve. The decision is made in Policy Confirm, by a person.
The whole loop, message by message
- 1Person or your endpoint to Assistant or agentA task: book a hotel, deploy a release
- 2Assistant or agent to Policy Confirmask_what_is_allowed
- 3Policy Confirm to Assistant or agentThe policy text: approval required
- 4Assistant or agent to Policy Confirmrequest_exception
- 5Policy Confirm to Assistant or agentAn ID, pending. The work pauses.
- 6Policy Confirm to AdministratorThe request, with who sent it
- 7Administrator to Policy ConfirmApproved
- 8Policy Confirm to Person or your endpointEmail to a person, signed webhook to an agent
- 9Person or your endpoint to Assistant or agentCheck the ID, or wake the run
- 10Assistant or agent to Policy Confirmget_exception_status
- 11Policy Confirm to Assistant or agentApproved, with the administrator's answer
- 12Assistant or agent to Person or your endpointThe work carries on, with the decision on record
You see every request, and who sent it
A person in the portal, a person through an AI assistant, or an AI agent with a named owner. Switch outside access off and every answer stops at once.
The whole surface: four tools, five endpoints
ask_what_is_allowedReturns the policy text that applies, with policy, version, heading and page.
read_policyReturns a whole section or policy, when the excerpts are not enough.
request_exceptionFiles an exception request and returns its ID.
get_exception_statusReads the status and the answer with that ID.
POST /v1/askThe question.
GET /v1/policiesThe policies and versions this key has.
GET /v1/policies/{id}The whole text of a policy or section.
POST /v1/exception-requestsFiles a request, returns the ID.
GET /v1/exception-requests/{id}The status and the answer.
MCP and REST give the same answer for the same question. Policy text and questions are treated as data, never as instructions.
AI governance for employees who use AI tools
The same policies your agents ask are the ones your people have read and confirmed.
Frequently asked questions
What is Policy Confirm Governance?
Policy Confirm Governance is a policy layer for AI. It is an MCP server and a REST API that AI assistants and AI agents ask before they act. It returns the text of the company's current approved policy, word for word, with the policy, version, heading and page, and it lets the AI file an exception request with the people who approve them.
What is AI agent governance?
AI agent governance is the set of rules and controls that decide what an AI agent may do on behalf of a company, and the record that shows the agent was given those rules. In practice the agent looks up the current policy before it acts, a person decides the exceptions, and both are logged.
How do Claude and ChatGPT connect to our company policies?
An administrator creates a company connector in Policy Confirm and chooses which policies it can read. The company adds that connector to Claude or ChatGPT, centrally or person by person. Nobody signs in. From then on the assistant asks Policy Confirm before it does something it is unsure is allowed.
How does an AI agent check company policy?
A developer gives the agent a key and one instruction: if unsure, ask Policy Confirm what is allowed. The agent calls POST /v1/ask, or the MCP tool ask_what_is_allowed, with a question in plain language. It gets back the passages that apply from the policies chosen for that key.
Does Policy Confirm tell the AI whether something is allowed?
No. It returns the policy text and its source and gives no verdict. The asking AI reads the text and concludes. That keeps every answer checkable: a person can open the same section of the same version and read the same words. No model writes an answer on our side, so a question costs a search.
What happens when no policy covers the question?
The response says not_covered. Not covered is not permission, and the tool descriptions tell the AI to ask a person. Policies that could not be searched are listed separately as unavailable, so an AI is never told that nothing was found in a policy that was never read.
How do AI agents handle policy exceptions?
Without a policy layer, an agent that meets a rule either stops, goes ahead, or follows an override the developer wrote. With Policy Confirm the agent files an exception request with the people who approve them, gets an ID, pauses the task, and is told by a signed webhook when an administrator has decided.
Can an AI approve its own exception?
No. There is no tool or endpoint that approves, rejects or changes a request. Administrators decide in Policy Confirm, and they see whether the request came from a person in the portal, a person through an AI assistant, or an AI agent and the owner of its key.
What is recorded when an AI asks?
The question, what was returned, and whether a company connector or a named agent key asked. No person is recorded on a question. A person is named only on an exception request they send. Organizations never see each other's policy text, requests or logs, and the data stays in your region, EU or US.
How is this different from Policy Intelligence?
Policy Intelligence is an assistant inside Policy Confirm that people ask directly, in the app or the policy portal. Governance is for AI outside Policy Confirm: the assistants your people already use and the agents your developers build. Both read the same list of policies an administrator has chosen for AI.
Give your AI one place to ask
Tell us which assistants and agents you want to connect, and we will show you how it fits your policies.