Source: https://frameworkrecipes.dev/nextjs/server-action-ownership/

# Authorize a Next.js Server Action at the database write

A Server Action is a server entry point. Hiding a button or protecting a layout does not authorize the mutation itself. Put identity scope and current state in the conditional write so the action remains protected when called directly.

Save this requirement in Perch and check it after each agent edit. The rule gives your agent a named check to run, a finding to repair, and the same command to recheck.

## Implement the Next.js boundary

Save this illustrative integration module as `app/orders/actions.ts`.

```
"use server";
import { revalidatePath } from "next/cache";
import { requireActor } from "@/lib/auth";
import { prisma } from "@/lib/db";

export async function cancelOrder(orderId: string) {
  const actor = await requireActor();
  const result = await prisma.order.updateMany({
    where: { id: orderId, tenantId: actor.tenantId,
             ownerId: actor.id, status: "pending" },
    data: { status: "cancelled" },
  });
  if (result.count !== 1) throw new Error("Order not available");
  revalidatePath("/orders");
  return { status: "cancelled" };
}
```

The order, inventory, or resource-lifetime scenario is adapted from Perch’s public [order-service source at commit 4af67af](https://github.com/lakeday-org/perch/blob/4af67af46d76ac99398d61c7ad0a45441760d4dc/test/fixtures/order-service/auth.py). This Next.js implementation is an illustrative adaptation.

## Integrate with your application

Implement requireActor with your existing verified server session, returning id and tenantId or throwing when signed out. Configure a server-only Prisma client with an Order model. Pass only orderId from the browser; do not accept actor identity as an action argument. updateMany is used so the scope is part of the write rather than a separate read.

## Exercise the boundary and failure paths

| Scenario | Expected outcome |
| --- | --- |
| Owned pending order | One row changes and path revalidation runs |
| Signed-out invocation | requireActor rejects before the query |
| Cross-tenant or cross-owner id | Zero updates, action throws |
| Two invocations for one pending order | At most one conditional update succeeds |

Add regression tests for these cases in your existing Next.js test project. Use separate connections or deliberately reordered completion where the case involves concurrency; a sequential happy-path test does not exercise that failure. Run the test command after creating the matching test file or suite:

```
npx vitest run tests/cancel-order.test.ts
```

The scenarios above specify tests to implement. A completed Perch source check below is separate from running these application integration tests.

## Introduce the specific agent regression

In a throwaway copy, replace this source span:

```
tenantId: actor.tenantId,
```

with:

```
// Remove the source span shown above.
```

Run the relevant negative test and the Perch command on that broken copy. Restore the corrected source before committing the application. The supplied mutation reproduces the exact regression for the rule check.

## Preserve the requirement as a Perch rule

Save this in `.perch/rules/perch-guide-nextjs-server-action-ownership.yaml` at the repository root, keeping your existing `perch.yaml`:

```
- name: action-write-authorization
  where: "app/orders/actions.ts"
  ensure: >-
    cancelOrder must obtain a verified actor and constrain updateMany by that actor tenantId and ownerId before mutating the order.
```

Install and authenticate the CLI once, then check the current working file:

```
npm install -g @lakeday/perch
perch login
perch check app/orders/actions.ts --rules action-write-authorization --json
```

Use Node 22 or newer. The framework can use another language; Perch’s CLI remains a Node command. A gated finding exits 3. Exits 1 or 2 mean the check did not complete and must be reported as a blocker.

## Inspect the captured rule check

On 2026-10-14, Perch using jev-latest checked the exact fixed and broken source provided here. The capture records SHA-256 hashes of both sources and the requirement.

| Source control | Exit | Outcome |
| --- | --- | --- |
| Broken | 3 | Rule finding |
| Corrected | 0 | No rule finding |

The rule distinguished these controls in this run. [Raw Perch capture](https://frameworkrecipes.dev/nextjs/server-action-ownership/capture.json) · [Exact sources and mutation](https://frameworkrecipes.dev/nextjs/server-action-ownership/source.json).

## Install the rule pack and configure your agent

[Download this rule pack ZIP](https://reporules.fyi/nextjs/server-action-ownership/rule-pack.zip) · [Download the YAML rules](https://reporules.fyi/nextjs/server-action-ownership/rules.yaml) · [Agent task](https://reporules.fyi/nextjs/server-action-ownership/agent-task.txt). The pack contains the rule, its example paths and the repair/recheck instructions. Review the `where` selector before using it in an existing project. Keep your root `perch.yaml`; install this rule as a separate file under `.perch/rules/`.

1. Install Perch using Node 22 or newer and sign in once:

```
npm install -g @lakeday/perch
perch login
```

1. Download the pack, inspect it, and extract it from your repository root. The extraction preserves any existing files:

```
curl -fL 'https://frameworkrecipes.dev/nextjs/server-action-ownership/rule-pack.zip' -o 'perch-guide-nextjs-server-action-ownership.zip'
unzip -n 'perch-guide-nextjs-server-action-ownership.zip'
```

The installed rule is `.perch/rules/perch-guide-nextjs-server-action-ownership.yaml`. Its selector matches `app/orders/actions.ts` in this example; adapt the selector to your application file before checking an existing project.

1. Configure the coding agent you use. Run one of these commands:

Claude Code:

```
perch setup claude-code
```

Codex:

```
perch setup codex
```

Cursor:

```
perch setup cursor
```

Pi:

```
perch setup pi
```

1. Ask the agent to edit the implementation and check the saved requirement:

> Use the installed Perch skill while editing app/orders/actions.ts. Preserve action-write-authorization. Run perch check app/orders/actions.ts --rules action-write-authorization --json after the edit. Read each finding and the affected code, fix the implementation, and run the identical check again after the fix. Keep the rule and regression tests intact. Run the application's relevant regression tests and report the commands and actual results. Exit 3 means a rule finding; exit 1 or 2 means the check did not complete. Report an unavailable or incomplete check as blocked. Do not claim the application tests ran if only the Perch check ran.

1. After repairing a finding, run the same check again and inspect the result:

```
perch check app/orders/actions.ts --rules action-write-authorization --json
```

Commit the downloaded rule and the installed agent configuration with your application. The rule file adds no guarantee of correctness; keep the regression tests from this guide.

With the base reference fetched, use `perch scan --since origin/main --filter type=lint` in CI.

## Framework references and verification scope

- [nextjs.org reference](https://nextjs.org/docs/app/guides/data-security)

The dated capture records the source check shown above. Implement the adapters, schema and regression tests described in this guide in your application. Unchanged requests reuse cached answers; fresh model judgments can vary. Model analysis sends relevant source to the configured service.

**Framework Recipes**

Implementation, failure path, check.

Published by Perch · © 2026 Verglas LLC. Framework Recipes is a Perch publication.

Perch’s MIT license covers the CLI; hosted model analysis is a paid service. Relevant source is sent to the configured model service.

[Perch CLI MIT license](https://github.com/lakeday-org/perch/blob/main/LICENSE) · [Article text](https://frameworkrecipes.dev/nextjs/server-action-ownership/index.md) · [Resource index](https://frameworkrecipes.dev/llms.txt)