Principle

Enforce permissions outside the model

A sentence in a prompt is guidance. An authorization check is a control.

About 1 min read

Before you use it

Use when
  • A workflow relies on prompt instructions such as 'never access other users' data' or 'only admins may delete.'

Keep this limit in mind

  • Deterministic authorization still needs correct policy, testing, auditability and secure identity handling.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Put access rules in deterministic downstream code or policy enforcement points that validate every protected request. The model can help choose an action, but it should not be the component that decides whether the caller is allowed to perform it.

An example

A delete API checks the user's role and record scope even when the agent confidently claims the deletion is allowed.

Check your result

Changing or bypassing the model prompt cannot bypass the downstream authorization rule.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingEnforce permissions outside the model

Evidence and sources
Supports

OWASP recommends enforcing critical authorization and privilege-separation controls independently from the LLM in deterministic, auditable systems.

External controls still need correct policy design and testing; moving a decision out of the prompt does not make it correct automatically.

LLM07:2025 System Prompt Leakage · Ensure security controls are enforced independently from the LLM

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details