Disclosure Request Preparation Agent · Use case
How can a police force or a defence organisation use an AI agent to prepare the response to a disclosure request on its own infrastructure?
A disclosure request preparation agent reads one freedom of information or subject access request, finds the records it covers through the records index, and lists the passages that may fall under an exemption, each with the exemption in the organisation's guidance. The disclosure officer decides every exemption and releases the response. The agent withholds nothing, redacts nothing, releases nothing and sends nothing to the person who asked.
The request is one page.
The records it covers are hundreds.
- ✗ 01A request has a date set by law, and the records it covers are spread across files, mailboxes and systems, many of them carrying personal data or a marking.
- ✗ 02Each page has to be read for what may not be released, by a small team with a queue, and a passage released in error cannot be called back.
Where it stops for a person
Always. The disclosure officer decides every exemption and releases the response.Always. It proposes, it does not decide: whether an exemption applies, where the public interest lies and what is released are the disclosure officer's decisions. It searches for records, not for people: it builds no profile of the person who asked or of anyone named in a record, and a subject access search is run only for the request in front of the officer. A record it could not open is listed, not left out.
It gathers and lists.
The disclosure officer decides and releases.
Step · 01
A disclosure officer uploads the request and sets the scope of the search.
Step · 02
The agent searches the records index through your own APIs, as the officer, and lists the records the request covers.
Step · 03
It reads each record and lists the passages that may fall under an exemption, with the exemption and the paragraph of the guidance.
Step · 04
It lists the records it could not open and the passages where the guidance is unclear.
Step · 05
The disclosure officer decides every exemption, applies any redaction, and releases the response.
Reads from · connectors
Your own APIs
The request, as an uploaded file; the records it covers, found and read through your own APIs with the operations that change something left out, as the signed-in officer and no more widely; and the organisation's disclosure guidance, indexed as a knowledge source.
Acts through · MCP servers
Nothing. It withholds no record, applies no redaction, changes no record and sends nothing to the person who asked.
What you set up
- Index the disclosure guidance and the list of exemptions, as your legal team has set them out, as a knowledge source.
- Import the description of the API to the records index and keep only the operations that read.
- Build the agent in Katonic Studio and test it on closed requests your officers have already decided.
- Publish it to the disclosure team, one kind of request first.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Requests and the records they cover hold personal data and marked material, and stay inside the organisation.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it decide what is withheld?
No. It lists the passages that may fall under an exemption, with the exemption. The disclosure officer decides every one.
Does it redact or release anything?
No. It has no tool that changes a record or sends a response. Redaction and release are done by the disclosure officer.
Can it read records the officer cannot?
No. It searches as the signed-in officer, and reads what that officer is cleared to read and no more.