Store a persistent decision for a tool from the settings surface. The in-stream ApproveAlways decision remains the other writer of the same rows; this endpoint exists so a grant flipped back to the policy default in settings can be re-granted without waiting for the next in-chat approval stop, and so a tool can be put on ask or denied outright. The `allow_always` policy only guards grants: it exists to keep the product from becoming more permissive, and a denial is strictly more restrictive, so it works in deployments that never enable approvals at all. An ask needs the approval gate to have any effect, so it is refused without one.

Changed on
post/api/v1beta/me/mcp-tool-approval-settings

Request

  • The document declares no server URL.
  • Auth: bearer_auth (a scheme the document does not define)

Request body

decision'always_allow' | 'ask' | 'denied'

A user's persistent decision for one MCP tool. Rows exist only while a decision is active; the absence of a row means the policy default applies.

mcp_server_idstring required
tool_namestring required

Response

decision'always_allow' | 'ask' | 'denied' required

A user's persistent decision for one MCP tool. Rows exist only while a decision is active; the absence of a row means the policy default applies.

idstring uuid required
mcp_server_idstring required
tool_namestring required

Changes

    • warning

      added the new ask enum value to the response property for the response status

    • info

      added the new ask enum value to the request property

    • info

      added the non-success response with the status

    • info

      added the new optional request property

    • info

      added the required property to the response with the status