fix(mcp): extend capability execution timeout - #2756
Merged
reachjalil merged 1 commit intoJul 14, 2026
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
|
@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
execute_capabilityouter budget from 45 seconds to 180 secondsFollow-up to #2750.
Root cause
#2750 extended external MCP tool requests to 120 seconds and their bounded lifecycle to 150 seconds. The engine-to-Den
execute_capabilitywrapper still returnedcapability_timeoutafter 45 seconds, so callers could receive a premature failure while the downstream operation was still within its allowed lifecycle.Impact
Long-running external MCP tools can now use the full downstream lifecycle. The 180-second outer budget leaves a 30-second margin for Den authorization and persistence work around the provider call. Existing provider request/lifecycle bounds, retry guidance, and error envelopes are unchanged.
Validation
pnpm exec bun test ee/apps/den-api/test/mcp-agent-timeouts.test.ts— passed, 9 tests / 23 expectationspnpm exec bun test ee/apps/den-api/test/external-mcp-diagnostics.test.ts -t "allows tool execution to use a longer bounded request timeout"— passed, 1 test / 4 expectationspnpm --filter @openwork-ee/den-api build— passedgit diff --check— passedSecurity and trust boundaries
Verification gaps