elaichi__access_request__create
File a request asking an org admin to grant access to a tool that just refused you — the operation behind a "blocked" result’s can_request_access flag. Only ever call this right after a tool call came back refused for permission or restriction (never for scope — that refusal is between you and your own client and no admin can fix it, so it never carries can_request_access). Pass the exact tool name and reason the refusal named, and the exact permission string too when reason is "permission" — never invent or guess a permission, and never pass one at all when reason is "restriction" (the request record must not become a way to learn which rule blocked you, so a restriction-reason call that names a permission is rejected). Filing twice for the same thing while the first request is still open does not create a second one — it returns the existing request (its own status tells you whether that was a fresh file or a repeat), so it is safe to call again if you are unsure whether one already exists. This only creates a RECORD for a human to review; it does not itself grant anything, and nothing about a tool becomes usable because you filed a request. Returns the request with can_withdraw.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Optional short context for the admin reviewing this, in the requester’s own words. | |
| tool | Yes | The exact tool name the refused call used, taken verbatim from the refusal — or, when resource_type is "connector", the connector slug. Never a name you composed yourself. | |
| reason | Yes | The refusal’s own reason, verbatim — "permission" or "restriction". Never "scope"; a scope refusal has no admin-side fix, so it never offers this operation in the first place. | |
| permission | No | Required, and must be a real permission name, when reason is "permission" — the exact string the refusal named. Omit entirely when reason is "restriction"; sending one there is rejected. | |
| resource_type | No | What is being asked for. Omit (or "tool") for the ordinary case: a tool call came back refused. Pass "connector" ONLY when the person is asking for a whole connected app they cannot reach at all — then `tool` carries the connector slug instead of a tool name. Never guess between the two: use whichever the refusal itself was about. |