Approve an action request and run its operation
Needs write on the operation’s resource (a user or an agent). Runs the operation now, as you, on the request’s arguments or your complete edited_arguments, in one step with the decision; if the operation refuses, you get its error and the request stays pending.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”Request Body
Section titled “Request Body ”object
Complete replacement arguments, validated and authorised as if proposed now. The original arguments stay on the request.
object
Responses
Section titled “ Responses ”Success
object
The registered operation proposed, for example tasks.update.
The operation’s flat arguments as proposed (the MCP shape: path, query and body fields in one object). Never changed after creation.
object
The complete replacement arguments a reviewer approved instead; null unless approved with an edit.
object
The principal (user or agent) that decided it; the system principal for an expiry.
What approval did: for an inline operation { events: [{ type, resource_type, resource_id }] }, the events it wrote; for a queued one the execution’s result. Null until executed.
The execution a queued approval created; absent or null until then and for operations that run inline.
The principal that proposed it: the source.