DPO Radio

A compliance team that extends Forseti into external tools has to answer one architectural question above all others: can an external integration write to our production records without a human in the loop? An "autonomous write" answer fails inspection. A "no writes allowed" answer fails adoption. The middle ground — every external write proposed, queued, previewed, and approved by a human before execution — is the only durable answer.
Forseti's MCP write tools enforce the middle ground by construction. The write surface is nine tools. Six are general: propose edit, attach evidence, generate a DOCX deliverable, create a task, bulk-create tasks, and convert a chat to a workflow run. Three work on forms: create a compliance form instance, update a form instance's fields, and submit a form instance. Every call to any of these tools enqueues a proposal in the in-product approval queue and returns a pending-write identifier with a 24-hour expiry. The proposal does not execute until an administrator reviews and approves it. The approve action runs the tool with the API-key holder's resolved permissions, not the proposing integration's identity.
The constraint is structural. There is no bypass for trusted keys. There is no "auto-approve" mode. There is no "skip the queue for low-risk writes". Every write is human-gated.
The deletion tool is not in the surface. Forseti has no delete tool of any kind, and the MCP connector does not invent one. An external integration cannot delete a record through the connector under any scope.
The external client proposes a partial record edit. The proposal carries the record identifier, the proposed field changes, and a rationale. The approval queue surfaces the preview against the current record state. On approve, the edit commits atomically as if the operator had made it; on decline, the proposal is closed without effect.
The external client proposes attaching an existing piece of evidence to a parent record. The approval queue shows the evidence preview, the proposed parent record, and the link rationale. On approve, the evidence is attached and the audit lineage records the MCP-initiated step.
The external client proposes rendering a DOCX deliverable through the platform's unified export pipeline. The approval queue shows the deliverable preview. On approve, the DOCX is generated and made available for the customer to download.
The external client proposes creating a task in the organisation task list. The approval queue shows the proposed task title, description, due date, and suggested owner role. On approve, the task is created with the suggested owner role; the operator picks the human assignee after creation. No external integration can assign a task to a specific user autonomously.
The external client proposes creating up to 50 tasks in one call. The approval queue shows the full list with per-row preview and a per-row approve / decline option. The administrator can approve, decline, or selectively edit the list before approve.
The external client proposes promoting a Forseti chat thread to a structured workflow run. The approval queue shows the chat reference, the workflow target, and the conversion plan. On approve, the chat becomes a workflow run with full lineage stitching.
Three tools cover the compliance-forms write surface: create an instance from a template, update an instance's field values, and submit an instance. Each one queues a proposal like every other write tool and runs only on approval, through the same forms service the in-product wizard uses. Required-field enforcement, tenant scoping, and the form's own audit trail are therefore identical whether a person or an approved proposal made the change. Submitting moves a form into its authority lifecycle, which makes it the proposal in this group an approver should read most carefully before approving.



Every write tool call emits a "write proposed" audit event with an explicit MCP source marker. The full lifecycle — proposed, approved, executed, declined, expired — emits five events stitched together by a shared proposal identifier.

No write tool can transition AI-generated evidence to approved. The transition is enforced as a human action under every code path, including MCP-initiated runs. No write tool can delete a record. No write tool can assign a task to a specific user autonomously; the suggested owner role is created, and the operator picks the human.

No Forseti token allowance can block a write proposal, because there is none. A proposal is enqueued whatever the month's consumption, and the administrator decides on it when they review it.

A consequential tool call shows its proposed effect for a reviewer inside ComplianceOne. An authorised person decides whether it proceeds. Use the approval queue to follow the decision.
Ready to see a Claude Code session propose a DPIA draft, land it in the approval queue, and execute on operator approve? Request a personalised demo.


Pilot a write-capable MCP key for a Claude Code DPIA-drafting integration. Measure the approval-queue cadence against your team's review tolerance.

Talk to our team about which write tools to enable for each integration and how to scope the approval-queue ownership.
No. Every write tool call enqueues a proposal in the in-product approval queue and returns a pending-write identifier with a 24-hour expiry. The proposal does not execute until an administrator approves it. There is no bypass for trusted keys.
No. Forseti has no delete tool of any kind, and the MCP connector does not invent one. An external integration cannot delete a record under any scope. Soft-delete and hard-delete are operator actions through the in-product surface.
No. The Create Task and Bulk Create Tasks tools carry a suggested owner role (DPO, Risk Lead, IT Lead, Compliance Lead) but no assigned user. After the task is created on approve, the operator picks the human assignee.
The hourly sweep moves expired proposals to an expired state and emits the "write expired" audit event. The calling integration receives a structured status on its next poll. Clients can re-propose by calling the tool again; there is no auto-revival.
Yes. The proposal can mix task types within a single bulk call up to the 50-row cap. The approval queue shows line-by-line preview; the administrator approves, declines, or selectively edits the list before approve.