wolfpack-mcp 1.0.108 → 1.0.110

package/dist/agentBuilderTools.js

@@ -162,6 +162,21 @@ export const AGENT_BUILDER_TOOLS = [
                     type: 'object',
                     description: 'The agent\'s own Ghost runtime settings, merged into every session\'s generated config. Two keys are honoured: "options" (e.g. {"max_turn_requests": 150} — the per-turn model request cap, default 200) and "agents" (per-agent overrides, e.g. {"coder": {"disabled_tools": ["agent"]}} to switch the sub-agent tool off). Other keys are ignored. Replaces the stored config as a whole; set to null to clear. Ghost runtime only — Claude Code agents ignore it.',
                 },
+                disabled_tools: {
+                    type: 'array',
+                    items: { type: 'string' },
+                    description: 'Tools the agent never gets, whatever starts the session (a task, a chat, a work-item pickup). Ghost names ("agent", "fetch"); Claude Code agents use Claude Code\'s own ("Task", "WebFetch") and "mcp__<server>__<tool>" for an MCP tool. Replaces the stored list; an empty array clears it. A task\'s own disabled_tools are added to these — a task narrows further, never widens.',
+                },
+                disabled_mcp_servers: {
+                    type: 'array',
+                    items: { type: 'string' },
+                    description: 'MCP servers the agent never gets, by name (e.g. ["wolfpack"]). The server is left out of the session config altogether rather than started and denied per tool. Replaces the stored list; an empty array clears it.',
+                },
+                disabled_skills: {
+                    type: 'array',
+                    items: { type: 'string' },
+                    description: 'Skills the agent never loads, by name (e.g. ["respond-to-notification"]). Replaces the stored list; an empty array clears it.',
+                },
                 ...ORG_SLUG_PROP,
             },
             required: ['agent_id'],
@@ -1060,6 +1075,9 @@ export async function handleAgentBuilderTool(name, args, client) {
                 llm_family: z.string().nullable().optional(),
                 api_key_permissions: z.array(z.string()).optional(),
                 config: z.record(z.unknown()).nullable().optional(),
+                disabled_tools: z.array(z.string()).optional(),
+                disabled_mcp_servers: z.array(z.string()).optional(),
+                disabled_skills: z.array(z.string()).optional(),
                 org_slug: orgSlugField,
             })
                 .parse(args);
@@ -1085,6 +1103,12 @@ export async function handleAgentBuilderTool(name, args, client) {
                 fields.apiKeyPermissions = rest.api_key_permissions;
             if (rest.config !== undefined)
                 fields.config = rest.config;
+            if (rest.disabled_tools !== undefined)
+                fields.disabledTools = rest.disabled_tools;
+            if (rest.disabled_mcp_servers !== undefined)
+                fields.disabledMcpServers = rest.disabled_mcp_servers;
+            if (rest.disabled_skills !== undefined)
+                fields.disabledSkills = rest.disabled_skills;
             const agent = await client.updateAgent(agent_id, fields, resolveOrg(parsed));
             return { content: [{ type: 'text', text: `Updated agent\n\n${text(agent)}` }] };
         }

package/dist/agentBuilderTools.test.js

@@ -192,3 +192,40 @@ describe('personal agents over MCP (#2273)', () => {
         expect(fn.mock.calls[0][1]).toBe(true);
     });
 });
+// #2525 — the three opt-out lists a profile carries, reachable over MCP so an
+// agent can be narrowed without hand-writing its config JSON.
+describe('profile-level disabled tools, MCP servers and skills (#2525)', () => {
+    const DISABLED_FIELDS = ['disabled_tools', 'disabled_mcp_servers', 'disabled_skills'];
+    function fakeUpdate() {
+        const updateAgent = vi.fn().mockResolvedValue({ id: 'agent-1' });
+        return { client: { updateAgent }, updateAgent };
+    }
+    it('update_agent advertises all three lists', () => {
+        const properties = toolNamed('update_agent').inputSchema.properties;
+        expect(Object.keys(properties)).toEqual(expect.arrayContaining(DISABLED_FIELDS));
+    });
+    it('sends the three lists under their stored names', async () => {
+        const { client, updateAgent } = fakeUpdate();
+        await handleAgentBuilderTool('update_agent', {
+            agent_id: 'agent-1',
+            disabled_tools: ['agent', 'mcp__wolfpack__create_issue'],
+            disabled_mcp_servers: ['wolfpack'],
+            disabled_skills: ['respond-to-notification'],
+        }, client);
+        expect(updateAgent.mock.calls[0][1]).toEqual({
+            disabledTools: ['agent', 'mcp__wolfpack__create_issue'],
+            disabledMcpServers: ['wolfpack'],
+            disabledSkills: ['respond-to-notification'],
+        });
+    });
+    it('an empty array is sent, so a list can be cleared', async () => {
+        const { client, updateAgent } = fakeUpdate();
+        await handleAgentBuilderTool('update_agent', { agent_id: 'agent-1', disabled_tools: [] }, client);
+        expect(updateAgent.mock.calls[0][1]).toEqual({ disabledTools: [] });
+    });
+    it('a field nobody named is left out, so it stays as stored', async () => {
+        const { client, updateAgent } = fakeUpdate();
+        await handleAgentBuilderTool('update_agent', { agent_id: 'agent-1', name: 'Scout' }, client);
+        expect(updateAgent.mock.calls[0][1]).toEqual({ name: 'Scout' });
+    });
+});

package/dist/index.js

@@ -383,7 +383,10 @@ const CreateWorkItemSchema = z.object({
         .enum(['S', 'M', 'L'])
         .optional()
         .describe('Size estimate: "S" (small), "M" (medium), "L" (large)'),
-    leading_user_id: z.string().optional().describe('User ID to assign as leading user'),
+    leading_user_id: z
+        .string()
+        .optional()
+        .describe('User ID to assign as leading user. AGENTS: you may put your own id here — filing work you already know you will do is the one assignment that is yours to make. Leaving it out is just as normal: the Delivery Lead assigns it instead. Either way the item waits in the backlog for a human to approve before you can pull it.'),
     category_id: z.string().optional().describe('Category ID to organize the work item'),
     radar_item_id: z
         .string()

package/dist/toolCatalogue.js

@@ -328,7 +328,7 @@ const SHARED_TOOLS = [
                 },
                 leading_user_id: {
                     type: ['string', 'null'],
-                    description: "User ID to assign as leading user, or null to unassign. Agents may not assign work to themselves — that is the Delivery Lead's decision.",
+                    description: "User ID to assign as leading user, or null to unassign. Agents may assign themselves only to a work item they created; who does anyone else's work is the Delivery Lead's decision.",
                 },
                 radar_item_id: {
                     type: ['string', 'null'],
@@ -806,7 +806,7 @@ const SHARED_TOOLS = [
         name: 'create_work_item',
         permission: 'mcp:work_items:create',
         description: 'Create a new work item in your current project (auto-selected for single-project users, or use list_projects first for multi-project). Requires mcp:work_items:create permission. ' +
-            'Agents: work you file lands unassigned in the backlog, whatever status you ask for, and waits there for the Delivery Lead to approve and assign it. ' +
+            'Agents: work you file lands in the backlog whatever status you ask for, and waits there for a human to approve it. Leaving it unassigned is the norm — the Delivery Lead assigns it. Put your own id in leading_user_id when you already know you will do it; that says who, not when, so it still waits for approval before you can pull it. ' +
             'ORDERED WORK: when you file a set of items that must happen in order, give each one depends_on ' +
             'naming the reference numbers it follows, rather than writing "Follows #2322" into the description — ' +
             'that way the board knows the order and the pickup gate enforces it. ' +
@@ -850,7 +850,7 @@ const SHARED_TOOLS = [
                 },
                 leading_user_id: {
                     type: 'string',
-                    description: "User ID to assign as leading user. Agents may not assign work to themselves — that is the Delivery Lead's decision.",
+                    description: 'User ID to assign as leading user. AGENTS: you may put your own id here — filing work you already know you will do is the one assignment that is yours to make. Leaving it out is just as normal: the Delivery Lead assigns it instead. Either way the item waits in the backlog for a human to approve before you can pull it.',
                 },
                 category_id: {
                     type: 'string',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wolfpack-mcp",
-  "version": "1.0.108",
+  "version": "1.0.110",
   "description": "MCP server for Wolfpack AI-enhanced software delivery tools",
   "main": "dist/index.js",
   "type": "module",