microsoft / microsoft/documentdb-mcp
Add Integ Tests for LIMIT enforcement verification
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 3
Description
Limits verification (automated integ-test, before release)
Set MAX_FIND_LIMIT=10, restart server, call find_documents requesting limit: 1000 → assert response has ≤ 10 documents.
Set MAX_INSERT_BATCH_SIZE=5, call insert_documents with a 6-doc array → assert reject.
Set MAX_RETURN_BYTES=1024, call find_documents against a collection with large docs → assert reject.
Set MONGODB_MAX_TIME_MS=1, call count_documents against a large collection → assert backend timeout error.
Set MAX_INSERT_BATCH_SIZE=25001 in env, attempt server startup → assert refuses with the actionable message.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the integration-test harness and the server configuration for MAX_FIND_LIMIT, MAX_INSERT_BATCH_SIZE, MAX_RETURN_BYTES, and MONGODB_MAX_TIME_MS. Exercise find_documents, insert_documents, and count_documents with the limits described, and verify the response caps, rejection, timeout, and actionable startup error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, typescript
- Domain
- backend, databases, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100