All lessons Leer en español

Security in depth · Unit 27 · Lesson 10 of 11

Give the model only needed context

Select the context needed for one task even when the caller can read much more.

4 minreadyShort lesson

Helpful before thisAI on offense

See all lessons in this topic

After this lesson you can

  • Choose a minimal authorized context and identify the separate retention question.

One idea. One situation. One reasoned decision.

How it works

Context can contain personal information, credentials, or business-sensitive records. Limit retrieval and tool access to the requester’s permitted scope and the task’s needs. Data minimization reduces unnecessary exposure and makes review easier. It does not replace provider, retention, or access-policy decisions. Do not assume a model needs the entire data store because a broader context might improve some answers.

Task need → Authorized retrieval → Minimum contextTask needAuthorized retrievalMinimum context
Follow the relationship: Task need → Authorized retrieval → Minimum context.

Permission to read does not make every field necessary

A fictional support analyst asks an assistant to recommend the documented update for case A. The analyst is authorized to read A and B, but the task concerns only A.

Record Available information
D1: case A Product, installed version, reported symptom
D2: case A Personal contact details and unrelated billing notes
D3: case B Another customer’s support history

Worked decision: begin with D1 and the approved product documentation. D1 supplies the facts needed to identify the applicable update. D2 and D3 add unrelated information to this task, even though the analyst’s general role can read them.

Enforce case and field scope before placing data in the model’s context. Removing details only from the final answer does not undo their earlier disclosure to the processing system. If a required fact is missing, retrieve the specific authorized information needed to resolve it rather than expanding to every accessible record.

Make a separate decision about where the context is processed, who can access it, and how long requests or logs are retained. Minimizing fields reduces exposure but does not establish an acceptable provider or retention arrangement. Record the task purpose and necessary data so another reviewer can evaluate the selection.

The key distinction: Usefulness does not grant access to unrelated information.

Check yourself

No timer. No penalties. Read the explanation and try again whenever you like.

  1. Which starting context best matches this task?

    Show the answer

    Correct answer: D1 plus the relevant approved product documentation. The product, version, and symptom support the update recommendation. The supplied task does not require unrelated personal, billing, or other-customer information.

Try it

  • WriteList the fields you would retrieve for the version recommendation in D1-D3. Explain why case scope, field selection, and provider retention need separate decisions.
References