Skip to content

boost-backend — Kagenti tool lifecycle routes, MCP server registration, and infrastructure admin (issue 5 of 15) #3301

@gabemontero

Description

@gabemontero

Labels: ready-to-code
Depends on: Issue 2

Implement Kagenti tool lifecycle routes (boost.tool.* permissions), MCP server registration routes, and Kagenti infrastructure admin routes (boost.kagenti.admin).

Note: The boost-tool resource type and lifecycle permissions apply to Kagenti tools (K8s workloads) only. MCP servers are registered endpoints without lifecycle governance. MCP tools are runtime-discovered children of MCP servers — they are not independently managed.

Tasks

From openspec/changes/security-safety-governance/tasks.md sections 4 and 5:

  • 4.1-4.4 Implement Kagenti tool lifecycle routes with boost.tool.* permissions
  • 5.1 Implement Kagenti admin routes with boost.kagenti.admin

MCP server registration (admin panel CRUD, connection test, auth chain config) — see spec below

Specifications

  • openspec/changes/security-safety-governance/specs/fine-grained-permissions/spec.md — Kagenti tool permission scenarios, infrastructure permissions
  • openspec/changes/agent-creation-discovery/specs/mcp-tools/spec.md — MCP server registration and auth chain (separate from Kagenti tool lifecycle)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions