{"version":"2.1.312","anchor":"mcp-skill-ask-is-now-held-for-a-person-in-the-held-calls-gat","canonical_anchor":"mcp-skill-ask-is-now-held-for-a-person-in-the-held-calls-gat","heading":"Loading an MCP skill can wait for a person to answer the permission prompt","tier":"use","area":"MCP","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/mcp-skill-ask-is-now-held-for-a-person-in-the-held-calls-gat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Loading an MCP skill can wait for a person to answer the permission prompt\n\nWhen loading an MCP skill needs permission, Claude Code can now hold the request until a person answers it\n\n**Unclear.** It is not clear whether the `mcpSkillAsk` setting is on by default or which kinds of session use this hold.\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, and some provide skills, which are packaged instructions Claude can load. When loading one of these skills needs your permission, Claude Code can now hold the request until a person answers. The reason it records is \"only a person answers the ask before an MCP skill loads\". This hold is controlled by a setting named `mcpSkillAsk`.\n\n**Why**\n\nSessions running without anyone watching, or sessions whose tool calls are being held for review, stop at the point an MCP skill would load instead of carrying on.\n\n- Area: MCP\n- Names: `mcpSkillAsk`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}