Knowledge Base

Overview

The knowledge base is what Pensar’s agents know about your workspace that they can’t learn from the target itself: how to reach it, what is expected behaviour rather than a vulnerability, and how your stack is put together. Each entry is a title and a Markdown body, and each has a priority that decides when agents get it.

Manage it under Settings → Agent Configuration → Context, on the Knowledge base tab.

The knowledge base requires an admin or owner role.

Priority

Every entry has one of three priorities. Change it from the dropdown on the entry’s row, or from inside the entry.

Priority	What agents do with it	Use it for
Always	Included in every pentest, retest and credential test	Rules every run must follow: how to reach the target, behaviour that should not be reported
On request (default)	Looked up by pentest and retest agents when it is relevant to what they are testing	Background: technology notes, where a feature lives, history of past findings
Off	Never used	Entries that are out of date but worth keeping

Credential tests only get Always entries. If logging in needs something first, such as joining a VPN, set that entry to Always.

A pentest takes its Always entries when it is launched, so changing which entries are Always applies from the next pentest. On request entries are looked up as the agent works, so turning one Off takes effect straight away.

The Always limit

A workspace can have up to 10 Always entries, totalling 20,000 characters of title and content. When the limit is reached, the budget in the table header turns amber and Always is unavailable in the dropdown, with the reason shown. Set an entry you need less to On request, or shorten one, to make room.

Adding an entry

Open the knowledge base

Go to Settings → Agent Configuration → Context and open the Knowledge base tab.

Write the entry

Click Add entry. Give it a title that says what it is about, and write the content in Markdown. Be specific: “Requests to /api/v2 need Content-Type: application/json or they return 415 before authentication” helps an agent more than “the API is strict about headers”.

Choose a priority

Leave it at On request, or choose Always if every run needs it. Click Add entry.

Pensar also adds entries itself. Marking a finding as a false positive adds an entry with your reason, shown with the source False positive, and agents can save what they learn during a run, shown as Agent. Both start as On request.

Seeing which entries are used

The table shows, for each entry:

30-day runs: how many runs in the last 30 days had the entry in their prompt or opened it.
Last used: when that last happened.

Turn on Unused in 30 days to list only the entries no run used.

Click an entry to open it. Recent use lists the runs that used it, marked in the prompt (an Always entry, or one attached at launch) or opened by the agent (an On request entry the agent looked up). View run opens that run.

Use this to steer the agents:

An On request entry that should have shaped a run but was never opened: set it to Always.
An Always entry that no longer matters: set it to On request to free up the limit.
An entry nobody uses and that is no longer true: edit it, or set it to Off.

Attaching entries to one pentest

To give a single pentest extra context, start a Custom Test from Launch pentest and type @ in the brief to reference knowledge base entries. Attached entries are included in that run alongside your Always entries. From the API, pass knowledgeEntryIds when launching a pentest.

From the API and MCP

Entries, including their priority, can be listed and edited through the REST API and the MCP server. There, creating, editing or archiving an Always entry also needs an admin or owner.