security_review
On-demand LLM security review of a project's deployed functions. Returns a structured Markdown report — findings (one per real risk), severity, and a fix.
Every plan can request a review. Paid plans get a longer report. Eligible paid plans also review when a preview is promoted. All plans use the same review model and minimal reasoning; only the report length limit differs.
Advisory only — never blocks anything. The deploy path never blocks on a pattern scan; it surfaces hits as warnings, and this tool is how you get the deep dive.
project_id is required (returns VALIDATION_ERROR if omitted). Backend failures are distinguishable, so a retry is never wasted on a persistent failure: a transient outage returns UPSTREAM_DOWN / UPSTREAM_RATE_LIMITED (retryable), while a persistent platform problem returns UPSTREAM_ERROR / CONFIG_ERROR (not retryable — a retry loop does not clear it).
Example:
{ "project_id": "my-saas" }
// Returns: { "findings": "## Findings\n### Auth bypass at api/checkout.ts ...\n...", "review_depth": "standard", "tier_unlocks_deep_review": false, ... }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": {
"project_id": "<project_id>"
},
"name": "security_review"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| focus | No | Optional area to focus the review on (e.g. "the new payments flow", "auth changes since last week"). Up to 500 chars. | |
| project_id | Yes | Project ID (UUID), subdomain, slug, or 'default'. Resolved server-side. |