emet_client_approve
Approve or deny pending client tags, or prepare a writer request for owner review and decision in EMET.
Instructions
Approve or deny a pending client tag, or prepare a new writer. decision prepare drafts a writer request: client, claimed tag, door (member or guest), reason, and correlation_id. The hub login prepares that draft. The server validates it. Validation is a check and is not approval. The owner decides a new writer on /owner/chooser with the owner session. No AI grants a writer, including the hub login and the retired owl account. The owner login may still approve or deny a pending client tag. Pending client tags are listed in emet_initialize and emet_status as client_approvals.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"tag": "<tag>",
"decision": "<decision>"
},
"name": "emet_client_approve"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| as | No | Required when the client_id already has approved tags: add keeps them all (several bots on one shared client); rename retires one | |
| tag | Yes | The pending client's tag, as listed in client_approvals.pending. For decision prepare, this is the claimed tag when claimed_tag is omitted. | |
| door | No | For decision prepare: member is a writer. Guest is not a writer. | |
| from | No | With as=rename on a client that has several approved tags: the tag being replaced | |
| client | No | For decision prepare: the client id the writer request names. | |
| reason | No | Note kept with the decision, or the reason on a prepared writer request. | |
| decision | Yes | ||
| claimed_tag | No | For decision prepare: the tag the writer would be known by. | |
| correlation_id | No | For decision prepare: 16 lowercase hex characters. The same id again returns the retained request. |