Fix: Block unauthenticated paid-API abuse and enforce session governance - #11
Open
mertcano wants to merge 1 commit into
Open
Fix: Block unauthenticated paid-API abuse and enforce session governance#11mertcano wants to merge 1 commit into
mertcano wants to merge 1 commit into
Conversation
This PR secures the chat and tool execution pathways by strictly enforcing server-validated sessions. It prevents unauthenticated callers from bypassing governance checks and consuming the server tenant’s paid services (such as web search, phone verification, and image generation) without a verified identity or spending rule. Changes: app/api/chat/route.ts: Removed the bypassable if (validatedSessionId) check. A verified sessionId and phoneNumber are now strictly required before triggering orchestrate(). Added a payload size limit (50KB) to prevent memory exhaustion lib/sapiom.ts: Modified sapiomFetch to explicitly require an agentName (session identifier) and disabled fallback to the unauthenticated defaultClient for paid API requests lib/tools.ts: Added strict context validation (context?.agentName) in tool executors to ensure billing and governance boundaries are respected before invoking paid services.
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.
This PR secures the chat and tool execution pathways by strictly enforcing server-validated sessions. It prevents unauthenticated callers from bypassing governance checks and consuming the server tenant’s paid services (such as web search, phone verification, and image generation) without a verified identity or spending rule.
Changes:
app/api/chat/route.ts: Removed the bypassable if (validatedSessionId) check. A verified sessionId and phoneNumber are now strictly required before triggering orchestrate(). Added a payload size limit (50KB) to prevent memory exhaustion
lib/sapiom.ts: Modified sapiomFetch to explicitly require an agentName (session identifier) and disabled fallback to the unauthenticated defaultClient for paid API requests
lib/tools.ts: Added strict context validation (context?.agentName) in tool executors to ensure billing and governance boundaries are respected before invoking paid services.