> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-agents/test-an-agent-safely.md).

# Test an agent safely

Before an agent uses live data or external tools, run a controlled task with safe records and limited credentials.

1. Give the agent a concrete objective and expected result. Test a normal request first.
2. Inspect which tools it uses, the parameters it sends, and the data it reads. Keep write tools disabled or scoped to test records until reviewed.
3. Try missing context, an irrelevant request, and a request for a record it should not access. Check how the agent responds when it cannot complete the task.
4. Test any workflow trigger or channel that will invoke the agent. Verify the same permissions apply there.
5. Record the prompt, outcome, and tool calls. Revise instructions or access, then repeat the case.

Use [Audit logs](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md) and relevant run history when available. For app access, see [Govern AI-generated apps](/access-and-sharing/overview.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/ai-agents/test-an-agent-safely.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.