Skip to main content
Glama
Sign In
F6 XDR MCP Server

F6 XDR MCP Server

Official
by F6-Security
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

xdr_get_mapping

Read-only

Retrieve all searchable fields, labels, categories, and supported operators for a specified XDR section so you can determine what to query before searching.

Instructions

Get all available search fields for an XDR section. Returns field names, labels, categories, and supported operators. Call this first to understand what you can search on.

Input Schema

NameRequiredDescriptionDefault
sectionYesSection name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications, application_versions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • changedInput schema / properties / section / description
      Previous value: -"Section name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications"New value: +"Section name, one of: alerts, incidents, emails, files, events, connections, assets, modules, audit, applications, application_versions"
    • changedInput schema / properties / section / enum
      Previous value: -[
-  "alerts",
-  "incidents",
-  "emails",
-  "files",
-  "events",
-  "connections",
-  "assets",
-  "modules",
-  "audit",
-  "applications"
-]New value: +[
+  "alerts",
+  "incidents",
+  "emails",
+  "files",
+  "events",
+  "connections",
+  "assets",
+  "modules",
+  "audit",
+  "applications",
+  "application_versions"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

The readOnlyHint and openWorldHint annotations already establish the safety profile, so the description's real contribution is disclosing the return shape (field names, labels, categories, supported operators), which is valuable given there is no output schema. It omits any note on result size or pagination, keeping it short of a 5.

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

Conciseness5/5

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

Three short sentences, zero padding, with the core verb and resource front-loaded and the return contents plus the usage cue following in priority order. Every sentence adds information.

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

Completeness4/5

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

For a one-parameter, read-only discovery tool with no output schema, the description covers purpose, output contents, and invocation timing, which is nearly everything an agent needs. A brief mention of the section enum's practical meaning would make it complete.

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?

Schema coverage is 100% and the single 'section' parameter is a fully enumerated string, so the schema already carries the parameter meaning. The description adds no extra semantics about what each section contains or how to choose one, which is the expected baseline-3 outcome when the schema does the work.

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 names a specific verb and resource: 'Get all available search fields for an XDR section', and it enumerates the returned content (field names, labels, categories, supported operators). It is clearly a metadata/schema-discovery tool, though it does not explicitly differentiate itself from the similarly named sibling xdr_get_filters.

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?

'Call this first to understand what you can search on' gives a concrete sequencing instruction, positioning it as a prerequisite before searching. It stops short of naming alternatives or when-not-to-use cases, so it falls just under the explicit routing bar.

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

Deploy Server

Other Tools