> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasiko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# `PUT /api/mcp/agents/{agent_id}/tools` — batch upsert tool rules.

> Each rule names its own `connector_id`, so the gate is per-connector: full
agent management, or (for each distinct connector referenced) that
connector's own owner acting on a connector already granted to this agent —
same relaxed rule as `set_connector_access`. An empty batch still requires
full agent management, since there's no connector to scope a narrower
check to.



## OpenAPI

````yaml /api-reference/openapi.json put /api/mcp/agents/{agent_id}/tools
openapi: 3.1.0
info:
  title: Nasiko API
  description: >-
    HTTP API for the Nasiko OpenRuntime: agents, coding harnesses, TokenOps,
    routing, MCP, and secrets. Spec is generated from annotated routes; some
    surfaces are documented on the hand-written pages alongside this file.
  license:
    name: ''
  version: 0.1.0
servers: []
security: []
tags:
  - name: secrets
    description: Encrypted per-user agent secrets
  - name: catalog
    description: >-
      Agent catalog: registration, discovery, versions, per-agent secrets, and
      source import
  - name: agents
    description: >-
      Agent lifecycle: deployments, LLM routing config, update/rollback,
      upload-and-deploy
  - name: orchestrator
    description: >-
      A2A dispatch: routing-engine/ReAct orchestrator and direct agent chat,
      plus routing stats
  - name: users
    description: >-
      User management: CRUD, roles, credentials, accessible agents
      (superuser-only)
  - name: usage
    description: Per-user token usage and cost reporting
  - name: observability
    description: Sessions, traces, spans, agent logs, and FinOps reporting
  - name: llm-router
    description: LLM routing presets, provider/model catalog, and tier→model registry
  - name: mcp
    description: >-
      MCP gateway: agent-facing JSON-RPC tool calls, connector
      registration/upload/sharing, credentials & OAuth, and per-agent tool
      permissions
paths:
  /api/mcp/agents/{agent_id}/tools:
    put:
      tags:
        - mcp
      summary: '`PUT /api/mcp/agents/{agent_id}/tools` — batch upsert tool rules.'
      description: >-
        Each rule names its own `connector_id`, so the gate is per-connector:
        full

        agent management, or (for each distinct connector referenced) that

        connector's own owner acting on a connector already granted to this
        agent —

        same relaxed rule as `set_connector_access`. An empty batch still
        requires

        full agent management, since there's no connector to scope a narrower

        check to.
      operationId: bulk_update_tools
      parameters:
        - name: agent_id
          in: path
          description: Agent id
          required: true
          schema:
            type: string
            format: uuid
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BulkToolUpdate'
        required: true
      responses:
        '200':
          description: Tool rules replaced
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/McpEnvelope'
        '403':
          description: Caller cannot manage a referenced connector on this agent
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/McpEnvelope'
components:
  schemas:
    BulkToolUpdate:
      type: object
      required:
        - rules
      properties:
        rules:
          type: array
          items:
            $ref: '#/components/schemas/ToolRule'
    McpEnvelope:
      type: object
      description: |-
        Doc-only schema for the standard MCP `ApiResponse` envelope
        (`{"data": …, "status_code": N, "message": "…"}`). Most `/api/mcp/*`
        payloads are service-layer `serde_json::Value` views, so `data` is
        documented as a free-form object; each route's response description says
        what it carries.
      required:
        - data
        - status_code
        - message
      properties:
        data:
          type:
            - object
            - 'null'
        message:
          type: string
        status_code:
          type: integer
          format: int32
          example: 200
          minimum: 0
    ToolRule:
      type: object
      required:
        - connector_id
        - tool_pattern
        - stance
      properties:
        connector_id:
          type: string
          format: uuid
        stance:
          type: string
        tool_pattern:
          type: string

````