Role
What job is it doing, for whom, and what is outside that job?
Governed AI agents
A governed AI agent is configured for one piece of work: you set its role, sources, skills, output and tools before it runs. Decide the approval and failure behaviour at the same time, before the agent touches anything real.
Search current policy and controls; compare material requirements; draft a findings table.
Four passages selected. One archived policy excluded from the answer scope.
Draft policy omits the annual continuity review. Two source links attached.
The configured permission requires a person to approve creation of the findings document.
This shows the steps Marella records. It is not every step the model takes.
What job is it doing, for whom, and what is outside that job?
Which document sets and external research routes may enter the work?
Which reusable capabilities can the agent call to complete bounded steps?
What must the output contain, omit and leave open for review?
Which actions are allowed, require confirmation or are denied?
Who decides whether the output or proposed action can be used?
Permission edge cases
A demo where everything works proves very little. Run the denied, uncertain and broken cases before granting broader scope.
Search an approved set of documents
Allowed
You can see which tool it called and which documents it used.
Create a draft document
Confirm
The run pauses; a named person approves or rejects before creation.
Publish to an external system
Denied
The call is blocked rather than merely discouraged in the prompt.
Tool returns malformed output
Fail closed
The agent surfaces the failure and does not treat partial data as success.
Question needs prohibited sources
Escalate
It says what is missing, or stops, rather than quietly looking somewhere it should not.
When not to automate
Keep the process manual, or use a simpler assistant, if the action cannot be safely reversed, approval cannot be enforced, the rules change case by case, or you could not show afterwards what happened.
Decision traces
Agent limits
AI agents FAQ
That depends on the configuration, because autonomy levels and per-tool permissions are both settings rather than fixed behaviour. Verify during evaluation which steps in your proposed workflow stop for a human confirmation and which do not.
Marella implements an MCP control layer for compatible servers. Native and third-party integrations still need authentication, permission and end-to-end testing.
Defined decision traces expose selected decisions and context. Event coverage and retention should be documented; do not treat them as an exhaustive record of system activity.
Test the permission edges first
Define approval points and failure cases before increasing autonomy.
Plan an agent evaluation