secure_prompt
Analyzes a raw coding prompt before code generation and returns a structured directive with security requirements for auth, input validation, and secrets. Detects your stack and attack surfaces to prevent vulnerabilities early.
Instructions
Shift-left security at the prompt level: analyze a raw coding prompt BEFORE any code is written and return a structured enhancement directive that embeds GuardVibe security requirements (auth checks, input validation, webhook signature verification, SQL injection prevention, secrets handling) into the prompt you are about to execute. Deterministic — no LLM, no network: triage verdict NO_MOD (prompt already specific and security-aware → proceed with the ORIGINAL prompt unchanged), LIGHT_MOD (inject missing security constraints only), or HEAVY_MOD (also surface clarifying questions — never invent answers to them). Detects stack (Next.js, Supabase, Clerk, Stripe, Prisma, Express, Hono...) and attack surfaces (auth, payments, file upload, user input, SQL, secrets, redirects) from the prompt text, matches them against GuardVibe's rule set, and returns verdict + intent summary + numbered [rule-id] requirements + rewrite directive. Call this with the user's prompt before generating code; prevents vulnerabilities before code generation instead of scanning after. Example: secure_prompt({raw_prompt: 'add login to my app'})
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"raw_prompt": "<raw_prompt>"
},
"name": "secure_prompt"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Known stack/framework context if the client has it (e.g. 'Next.js app router, Supabase, Stripe') | |
| raw_prompt | Yes | The user's original coding prompt, verbatim |