get_approvals_role_requests
Calls GET /api/approvals/role-requests as the signed-in person · REST reference
Role-change request queue (stub)
NOT IMPLEMENTED. The handler is a constant: it always answers an empty list with count 0 and never reads any store, so an empty result here means the feature does not exist, not that the queue is clear. It exists so the Approvals page renders both of its tabs. Because there is no data access there is nothing to fail — this endpoint cannot answer 500. It is behind the platform-staff gate.
Arguments
This tool takes no arguments.
Example call
A client sends this over the MCP session; Claude and other agents build it for you. The values are placeholders — the shape is real.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_approvals_role_requests",
"arguments": {}
}
}Result
On success (HTTP 200) the tool returns one text item holding the API's JSON, pretty-printed.
Always an empty list.
{
"count": 0,
"data": [
{}
]
}Fields
| Field | Type | Description |
|---|---|---|
count | 0 | |
data | array of object |
When it fails
A failed call returns isError: true with the API's message as text.
403Authenticated, but the caller holds none of the required permissions.
What the model is shown
This is the tool exactly as the server lists it in tools/list. The description starts with the REST call it makes.
{
"name": "get_approvals_role_requests",
"description": "GET /api/approvals/role-requests — NOT IMPLEMENTED. The handler is a constant: it always answers an empty list with count 0 and never reads any store, so an empty result here means the feature does not exist, not that the queue is clear. It exists so the Approvals page renders both of its tabs. Because there is no data access there is nothing to fail — this endpoint cannot answer 500. It is behind the platform-staff gate.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false
}
}