delete_v1_framework_roles_user_role
Removes one (user, role) grant in the caller's org.
Removes one (user, role) grant in the caller's org. Manager-only. Answers 204; a grant that does not exist is not found.
| Tool | delete_v1_framework_roles_user_role |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 2 required |
| Operation | DELETE /v1/framework/roles/{user}/{role} |
| Product | framework |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
role | string | yes | — | — | Role is the role to revoke, from the path. A role name containing a space ("System Manager") arrives percent-encoded and is decoded before it is matched against the stored assignment. |
user | string | yes | — | — | User is the assignee whose grant is being revoked, from the path. |
tools/list declares a type and a description for each field and nothing further. The Required column is taken from DELETE /v1/framework/roles/{user}/{role}, the operation this tool dispatches to — the same declaration the REST API validates against. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "delete_v1_framework_roles_user_role",
"arguments": {
"role": "<role>",
"user": "<user>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
delete_v1_framework_roles_user_role | DELETE /v1/framework/roles/{user}/{role} | framework | Removes one (user, role) grant in the caller's org. |
The same capability over plain HTTP is in the framework API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
delete_v1_framework_doctypes_name
Removes a DocType and every document stored under it. The definition and its data go together — a document with no schema can be neither validated nor read back — so there is no undo. Manager-only.
get_v1_framework_doctype
Returns the caller org's documents of one DocType, filtered, ordered and projected by the query.