{"version":"2.1.260","anchor":"new-admin-config-key-mcptooltimeoutsec-caps-mcp-tool-call-d","canonical_anchor":"new-admin-config-key-mcptooltimeoutsec-caps-mcp-tool-call-d","heading":"New admin config key: mcpToolTimeoutSec caps MCP tool call duration","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/new-admin-config-key-mcptooltimeoutsec-caps-mcp-tool-call-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### New admin config key: mcpToolTimeoutSec caps MCP tool call duration\n\nAdmins can now cap how long MCP tool calls are allowed to run.\n\nA new managed-config field, `mcpToolTimeoutSec`, lets an org set a per-call timeout of 60-3600 seconds for MCP tool calls. Cowork\/chat already defaulted to 180s, but Code sessions previously had no desktop-imposed MCP timeout; setting this key now gives them one, and the desktop's own request deadlines toward managed and user-added local MCP servers follow this value.\n\n- Area: MCP\n- Names: `mcpToolTimeoutSec`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}