Problem
MCP clients need a safe way to save and run searches, but anonymous persistence and unbounded schema can create privacy and complexity problems.
Proposed solution
Add authenticated saved-search MCP tools that support list, create, delete, and run actions using the #166 model, with no anonymous persistence and bounded schema validation in the tool contract.
Acceptance criteria
- Authenticated list/create/delete/run behavior.
- No anonymous persistence.
- Bounded schema and validation for saved searches.
- Clear permissions and ownership semantics.
- Test coverage for create/update/delete and invalid payloads.
Privacy and trust
Saved searches should be accessible only to the authenticated owner, and query payloads must not be stored in a way that leaks personally identifiable or sensitive search intent beyond the required owner context.
Dependencies
- MCP tool contract and authentication layer.
- Search model and persistence boundaries.
- Validation and test scaffolding.
Problem
MCP clients need a safe way to save and run searches, but anonymous persistence and unbounded schema can create privacy and complexity problems.
Proposed solution
Add authenticated saved-search MCP tools that support list, create, delete, and run actions using the #166 model, with no anonymous persistence and bounded schema validation in the tool contract.
Acceptance criteria
Privacy and trust
Saved searches should be accessible only to the authenticated owner, and query payloads must not be stored in a way that leaks personally identifiable or sensitive search intent beyond the required owner context.
Dependencies