delete · projects:write
Remove a member
Remove a member
WriteDestructiveIdempotent
REST
delete
/api/v1/members/{id}curl "https://herculeradar.com/api/v1/members/:id" \ --request DELETE \ --header "Authorization: Bearer hr_live_…"
MCP
Tool name remove_project_member. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.
Remove a member from the project. Invites are not this tool.
Parameters
| idrequired | string | User id |
Response
{
"data": {
"deleted": true,
"user_id": "uuid"
},
"meta": {
"capability": "remove_project_member",
"requestId": "req_9f2b4a8c1d0e",
"idempotencyReplayed": false,
"docs": "https://herculeradar.com/docs/reference/remove_project_member"
}
}Authorization
Requires the projects:write scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.
Send an Idempotency-Key header. A completed response is replayed for 24 hours, so a retry after a timeout cannot create a duplicate.