my_capabilities
What your agent token may DO. The write surface is the authoritative scope manifest (the platform enforces the same set); reads cover the allowed domains with secrets redacted. Writes apply only to contracts in your grant pool.
Access: read-only — safe to call repeatedly, changes nothing
Available at: /mcp/, /mcp/readonly/
Hints declared to MCP clients (ToolAnnotations)
| Hint | Value |
|---|---|
readOnlyHint | true |
destructiveHint | false |
idempotentHint | true |
openWorldHint | false |
Parameters
Section titled “Parameters”This tool takes no parameters.
Example call
Section titled “Example call”Send inside an initialized MCP session (see Connecting). Every parameter is shown with a typed placeholder; drop the optional ones you do not need — but for defect/task tools the QA fields are what keeps a report out of quarantine.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "my_capabilities", "arguments": {} }}Returns
Section titled “Returns”| Field | Type | Description |
|---|---|---|
writes | array of object | Every write your token class may perform |
writes[].method | string | HTTP method of the allowed write |
writes[].path | string | Path template of the allowed write |
writes[].capability | string | Capability the write requires |
writes[].entity | string | Entity the write targets |
writes[].pool_check | boolean | True when the target must be in your contract grant pool |
writable_fields | object | Field-level allowlist for agent writes |
writable_fields.fields | array of string | Field names an agent write may carry |
writable_fields.by_entity | object | Writable fields per entity |
writable_fields.applies_to | array of string | Operations the field allowlist applies to |
writable_fields.note | string | What happens to keys outside the allowlist |
reads | string | What you may read and through which channel |
note | string | Scope rule for writes |
If it fails
Section titled “If it fails”| Symptom | Cause | Action |
|---|---|---|
401 | Token missing/expired | Tokens are issued by the platform owner via POST /api/v1/auth/agent-token (superuser-only) — ask for a re-issue. ⚠️ A new token replaces your grant set |
403 / capability error | Your token lacks the capability or the contract grant | Check my_capabilities first; ask the owner for the grant |