MCP Server

List all scans in your workspace.

Parameters: None

Returns: A list of scans with their IDs, labels, statuses, scan types, branches, and timestamps.

Example prompt: “Show me all my Pensar scans.”

Get detailed information about a specific scan.

Parameters:

Returns: Detailed scan information including workspace name, status, error messages, issue count, and whether a report is ready.

Example prompt: “What’s the status of scan xyz-789?”

Queue a hosted pentest in the authenticated workspace. The scan runs asynchronously; an identical active launch may be reused.

Parameters:

Exact endpoint arguments:

{
  "endpointIds": [
    "7e4fe67a-61e5-4aa5-b93a-6871b470aaef",
    "59e9b6d5-d13b-4912-9e46-a1e801c1d053"
  ],
  "scanLevel": "full"
}

Find discovered endpoint IDs with pensar apps endpoints <appId> in the Apex CLI or GET /apps/:appId/endpoints in the REST API. MCP does not expose endpoint discovery.

Exact lists use full depth and test the supplied endpoints without commit-based narrowing. Each selected application must be ready to test. Omit endpointIds to test eligible workspace applications at priority depth by default.

Invalid IDs or incompatible arguments return a tool error without expanding the requested scope.

Returns: The queued scan’s scanId, label, status, and confirmation message. Use get_scan with that ID to check completion. Failures are MCP tool errors (isError: true).

Example prompt: “Use dispatch_pentest with these two discovered endpoint IDs only: 7e4fe67a-61e5-4aa5-b93a-6871b470aaef and 59e9b6d5-d13b-4912-9e46-a1e801c1d053. Then check the returned scan ID until it completes.”

List security issues with optional filtering.

Parameters:

Returns: A list of issues with their IDs, issueLabel references (VULN-000123), console urls, titles, severities, statuses, and file locations. Closed issues also carry closedAt, closedDisposition and duplicateOf, so a closed finding is not mistaken for a resolved one; all three are null while the issue is open.

Example prompt: “Show me all critical open issues.”

Get detailed information about a specific security issue.

Parameters:

Returns: Full issue details including the issueLabel reference, the console url, the finding name, description, affected file and lines (startLineNumber, endLineNumber), CWE classification, branch, proof-of-concept, endpointId, applicationId, and workspace information. A closed issue adds the full close record: closedAt, closedDisposition, duplicateOf, closedMethod, closedReason, and closedComments.

Example prompt: “Give me the details on VULN-000123.”

Update a security issue’s status, disposition, or inventory endpoint association.

Parameters:

Pair closedDisposition with status: "closed" — without it the finding reads as Resolved whatever the reason says. Reopening clears it, and false-positive never carries one. other is not accepted, as it is being retired from the vocabulary.

A duplicate close must name its original in duplicateOf, another issue in the same workspace that is not itself closed as a duplicate, and no other disposition may carry one.

Endpoint updates validate workspace ownership, keep applicationId synchronized to the endpoint’s application, and reject duplicate (pentest, title, endpoint) associations.

Returns: The updated issue details, including close metadata plus endpointId and applicationId.

The change is also applied to the finding’s linked GitHub, Linear and Notion tickets.

Example prompt: “Close issue abc-123 as risk-accepted, we have a WAF rule in front of it.”

List all available fixes for a security issue.

Parameters:

Returns: A list of fixes with their IDs and affected file paths.

Example prompt: “Are there any fixes for issue def-456?”

Get detailed information about a specific fix, including the code diff.

Parameters:

Returns: The fix details including the file path, a unified diff of the changes, an explanation of what the fix does, and the related issue ID.

Example prompt: “Show me the diff for fix ghi-789.”

List agent execution logs for a specific issue. Useful for understanding how the agent discovered and verified a vulnerability.

Parameters:

Returns: A list of agent log entries with timestamps, levels, roles, and content.

Example prompt: “Show me the agent logs for issue abc-123.”

Search agent execution logs by text pattern with configurable context lines.

Parameters:

Returns: Matching log entries with surrounding context.

Example prompt: “Search the agent logs for issue abc-123 for mentions of SQL injection.”

List knowledge base entries, newest first.

Parameters:

Returns: Entries with their ID, title, content, category, status, source, tags, createdBy, and timestamps.

Example prompt: “What does Pensar know about our tech stack?”

Get one knowledge base entry.

Parameters:

Returns: The full entry.

Add a knowledge base entry, attributed to you. Requires a user credential.

Parameters:

Returns: The created entry.

Example prompt: “Add a technology note to Pensar that our API sits behind a WAF.”

Edit a knowledge base entry. Omitted fields are unchanged; tags replaces the existing list. Requires a user credential.

Parameters:

Returns: The updated entry.

Archive a knowledge base entry so agents stop using it. The entry stays readable. Requires a user credential.

Parameters:

Returns: The archived entry.