For the complete documentation index, see llms.txt. This page is also available as Markdown.

UpdateUserMCPTools

Grant a user access to MCP tools, or revoke it.

Only an Administrator can call this route, and it cannot be run as another user. The MCP module must be enabled.

Tools are named as in the MCP server, e.g. 'find_projects'. Get Available MCP Tools lists every name that is accepted, and Get User MCP Tools lists the ones the user has now. A later operation on the same tool wins. When the request adds a tool, the user is given an API key if they have none.

Only access given to the user directly is changed. A tool that one of their groups gives them stays available after it is removed here, until Update Group MCP Tools removes it from the group.

Headers

PATCH /api/ss/user/:id/mcp-tools HTTP/1.1
Host: demo.attackforge.com
X-SSAPI-KEY: APIKey
Content-Type: application/json

Request

Path Parameters

id - string | required

ID of the user. Must be a 24-character hexadecimal id.

Body

operations - list of objects | required

Delegations to grant or revoke. At least one operation is required.

  • tools - list of strings | required

    • List of tool names. At least one is required.

  • type - string | required

    • Must be either 'add' or 'remove'

Example

Request

Response

Access and failures

Errors are returned in error:

  • Unauthorized - the caller is not an Administrator.

  • User Not Found or Error Finding User - the user could not be found.

  • Unknown tools: a, b - a tool is not one of the MCP tools. Nothing is applied.

  • Error Granting MCP Tools or Error Revoking MCP Tools - the change could not be saved. Tools are granted before any are revoked, so a revoking error means the grants were applied.

Last updated