Repository navigation
feat: enforce requester-bound team actions - #16
Draft
ishankunam wants to merge 1 commit into
Draft
ishankunam wants to merge 1 commit into
ishankunam wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 29, 2026
ishankunam
added this pull request to stack #25
September 30, 2026 05:04
This was referenced Sep 30, 2026
This branch was successfully deployed
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
1 participant
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.
Vee's service permissions and confirmation rules previously depended on instructions. This change routes organizational retrieval and mutations through guarded tools. External writes require the original Slack requester to approve the exact call and arguments, with the existing exception for preparing AgentMail drafts.
GitHub repository, branch, issue-create, and draft-PR restrictions are checked before execution. The Slack review renders the complete arguments before the approval buttons. An atomic Redis REST write-attempt record prevents an interrupted Eve step from dispatching the same call again. Writes fail closed until this store is configured. No provider writes are automatically retried.
Shared organizational grants remain unchanged. Provider tool allowlists and bounded read retries replace raw MCP connections. Shared Notion search refuses connected-source AI search. Sessions requesting private Slack context cannot export that content through other services or actions. Unrestricted shell execution, child agents, and provider-managed web search are disabled because they bypass those guards. The final stacked PR also disables the generic URL-fetch tool.
Stack: 2 of 3, based on #15 and followed by #17. Each PR targets its predecessor. Keep this draft until the complete stack and two-user pilot pass.
Validation:
Deployment requires
VEE_ACTION_REDIS_REST_URLandVEE_ACTION_REDIS_REST_TOKENfor a durable Redis REST store with atomicSET NXand no eviction of write records. Reads do not require the store. The final stacked PR contains the setup and rollout checklist.