3 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	3a4488b41e	The company's MCP tools under the guardrails, a rate and a breaker ... A tool's answer is read by the caller's policies as the prompt it becomes, so an instruction planted in a ticket is withheld and personal data redacted; its arguments are read before they leave. ctl mcp add --rate bounds each caller's calls a minute to a server (migration 0050), and five failures in a row take a server out for a minute, its tools off the list. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-20 23:00:22 +02:00
Ilker ManapandClaude Opus 5.5	4eb49d0e4c	The cluster as a read-only MCP server, llmgw:admin ... Its tools say what llmgw ctl does: cluster_status, list_nodes, list_models, list_replicas, explain_placement, node_logs; none changes anything. The admin API serves it at POST /api/v1/mcp, and the gateway answers a server registered as llmgw:admin in its own process, so no token is kept and each control plane serves it. ctl mcp add takes --bearer-file for a token sent as Authorization: Bearer. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-20 17:18:28 +02:00
Ilker ManapandClaude Opus 5.5	4453f469e1	Company MCP servers are registered with ctl mcp, and tools granted with keys limits --tools ... llmgw ctl mcp add|list|remove|test and /api/v1/mcp/servers keep the servers; a token given with --secret-file is kept in the store, sealed, and named by reference. keys limits --tools, and the console's limits form, grant tools as patterns. Documented in install.md and clients.md. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-20 12:50:55 +02:00