Tin 3489e650da fix(mcp): use a toolset row's stored tool name as written ... A toolset row is {server_id, tool_name}. The server is already identified by server_id, so the stored name is the tool's own name and there is nothing for a prefix to disambiguate. Resolution nevertheless reduced the stored name by the server's wire prefix, which is a guess about a string that carries no such marker. The wire prefix is added on the way out and is not part of any tool's identity, so when a native tool name happens to begin with it the guess renamed the tool: a row for greyhound_internal_events on a server prefixed greyhound resolved to internal_events. That is a different tool on the same server, so the selected tool disappeared from /toolset/<name>/mcp and an unselected sibling was served, and executed, under the selected tool's wire name. Toolsets are the tool-level permission boundary, so the row granted access to something never selected. Match the stored name as written and keep stripping the prefix off the live name only. This is the only producer that rewrote allowlist values; every other one stores what the admin typed, so the tools/list filter, the tools/call permission check, the REST listing and the Responses API path are all corrected without touching them. A row that stores an already-prefixed name no longer resolves. Such a row names a tool that does not exist on the server, and the dashboard has never written one; it was only ever accepted because of the guess this removes.		2026-07-24 17:06:08 -07:00
..
mcp_server	fix(mcp): use a toolset row's stored tool name as written	2026-07-24 17:06:08 -07:00