> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Restrict What an AI Agent Can Reach
- URL: https://blog.jestor.com/restrict-what-an-ai-agent-can-reach/
- Published: 2026-09-17T22:36:44.000Z
- Updated: 2026-09-17T22:36:44.000Z
- Author: Bruno Bannach

To **restrict what an AI agent can reach**, the boundary has to be explicit and enforced by the platform rather than by the agent's instructions.

## Why instructions are not a boundary

Telling an agent not to do something is guidance, not control.

- Instructions that can be misinterpreted in an edge case
- No enforcement if the agent behaves unexpectedly
- No record of what the boundary was supposed to be
- Nothing to show a reviewer asking what it could touch

## What to define

| Control               | What it determines                        |
| --------------------- | ----------------------------------------- |
| **Field permissions** | Exactly which fields it may edit          |
| **Knowledge base**    | What it answers from                      |
| **Confirmation gate** | Whether a person approves before it acts  |
| **Process scope**     | Which tables and pipelines it operates on |

## How to configure it in Jestor

1. Open the agent configuration in **Jestor** and go to the field permissions.
2. Select only the fields it should fill — status, priority, category, sentiment.
3. Leave authority-bearing fields unselected; the agent cannot access them at all.
4. Attach only the documentation it should answer from.
5. Add a confirmation checkbox on critical processes so a person approves before it acts.

## Why choose Jestor for governed AI?

**Jestor** enforces the boundary in configuration rather than in the prompt, which means anything unselected is unreachable regardless of how the agent interprets an instruction.

That explicitness is also what makes the boundary reviewable: someone asking what the agent can touch gets a list rather than a description.

## Frequently Asked Questions

### Can the agent reach unselected fields?

No, they are inaccessible to it. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Are instructions enough?

No — field permissions are the enforcement.

### Can I require human approval?

Yes, with a confirmation checkbox.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.