Skip to main content
Glama
panther-labs

Panther MCP Server

Official

list_detections

Read-only

Retrieve and filter security detections from Panther by type, severity, state, tags, and other criteria to monitor rules and policies.

Instructions

List detections from your Panther instance with support for multiple detection types and filtering.

Note: The output_ids filter is applied client-side after fetching all results from the API, as the Panther REST API does not support server-side filtering by outputID. For more efficient API-level filtering, consider using the 'tag' parameter if your detections are tagged by environment.

Permissions:{'all_of': ['View Rules', 'View Policies']}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detection_typesNoOne or more detection types - rules, scheduled_rules, simple_rules, or policies.
cursorNoOptional cursor for pagination from a previous query (only supported for single detection type)
limitNoMaximum number of results to return per detection type
name_containsNoSubstring search by name (case-insensitive)
stateNoFilter by state - 'enabled' or 'disabled'
severityNoFilter by severity levels - INFO, LOW, MEDIUM, HIGH, or CRITICAL.
tagNoA case-insensitive list of tags to filter by.
log_typeNoA list of log types to filter by (applies to rules and simple-rules only).
resource_typeNoFilter by resource types (applies to policies only) - list of resource type names
compliance_statusNoFilter by compliance status (applies to policies only) - 'PASS', 'FAIL', or 'ERROR'
created_byNoFilter by creator user ID or actor ID
last_modified_byNoFilter by last modifier user ID or actor ID
output_idsNoClient-side filter by destination output IDs. Filters results after fetching from API to include only detections with at least one matching outputID.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds valuable behavioral context beyond the readOnlyHint annotation, such as the client-side filtering caveat for 'output_ids' and the efficiency tip for using 'tag'. It also includes permissions information ('View Rules', 'View Policies'), which is not covered by annotations. No contradictions with annotations exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the core purpose, followed by important notes and permissions. It avoids unnecessary repetition, but the permissions section could be integrated more smoothly, and the note about client-side filtering is slightly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (13 parameters), rich schema coverage (100%), annotations (readOnlyHint), and the presence of an output schema, the description is complete. It covers key behavioral aspects like filtering nuances and permissions, leaving no critical gaps for the agent to understand the tool's use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the input schema already fully documents all 13 parameters. The description does not add significant semantic details beyond what the schema provides, such as explaining interactions between parameters or edge cases, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'List detections from your Panther instance with support for multiple detection types and filtering.' It specifies the verb ('List'), resource ('detections'), and scope ('Panther instance'), but does not explicitly differentiate it from sibling tools like 'get_detection' or 'list_alerts', which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by noting that 'output_ids' filtering is client-side and suggesting 'tag' for more efficient API-level filtering. However, it does not explicitly state when to use this tool versus alternatives like 'get_detection' or 'list_alerts', which would be needed for a score of 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/panther-labs/mcp-panther'

If you have feedback or need assistance with the MCP directory API, please join our Discord server