Find tenant-boundary gaps in request handling
For engineers reviewing multitenant services; returns route-level enforcement judgments.
Works with
- Codex
- Cursor
- GitHub Copilot
The prompt128 words · 4 blanks
What you fill in
- Service request paths
[service_code]ExampleRoutes, middleware, data access, jobs, cache code, and policy configuration - Tenancy model
[tenancy_model]ExampleShared database and schema - Main enforcement layer
[auth_location]ExampleService layer policies - Entry points to inspect
[sample_routes]Example8
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Find tenant-boundary gaps in request handling”.
- 2Fill in the 4 blanks. service request paths, tenancy model, main enforcement layer and entry points to inspect — the only things the prompt cannot know.
- 3Copy and paste it into Cursor. It also works with Codex and GitHub Copilot.
About this prompt
“Find tenant-boundary gaps in request handling” is a intermediate coding prompt. For engineers reviewing multitenant services; returns route-level enforcement judgments. It is 128 words long and written to get a usable answer on the first message, in Codex, Cursor and GitHub Copilot or any other chat assistant. Good for: analysis, security, audit, code review and architecture. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
