보안 MCP 도구

이 제품은 선택한 Datadog 사이트에서 지원되지 않습니다. ().

개요

Datadog MCP 서버를 사용하면 AI 에이전트가 Model Context Protocol(MCP)을 통해 보안 데이터를 쿼리할 수 있습니다. security 도구 세트는 Cursor, Claude Code 및 OpenAI Codex와 같은 AI 클라이언트가 보안 신호 및 탐지 결과에 접근할 수 있도록 하여 자연어를 사용해 위협을 조사하고 보안 태세를 분석할 수 있게 합니다.

이 페이지에서는 원격 Datadog MCP 서버의 security 도구 세트를 설명합니다. 로컬에서 실행되고 개발 환경에서 소스 코드를 스캔하는 Code Security MCP 서버에 대해서는 Code Security MCP 서버를 참조하세요.

사용 사례

security 도구 세트를 사용하여 다음을 수행할 수 있습니다.

  • 보안 신호 분석 및 이해하기: AI 에이전트에게 최근 심각도가 높은 Cloud SIEM 신호, App & API Protection 경보 또는 Workload Protection 위협을 노출하도록 요청하고, 패턴 및 영향을 받는 리소스에 대한 요약을 받으세요.
  • 보안 신호 분류하기: 일치하는 신호 집합에서 분류 상태 또는 담당자를 한 번에 업데이트합니다.
  • 보안 태세 분석하기: SQL을 사용하여 Cloud Security 전반의 탐지 결과를 쿼리하여 잘못된 구성, 취약점 및 ID 위험이 어떻게 분포되어 있는지 이해합니다.
  • 특정 탐지 결과 조사하기: 범위, 영향을 받는 리소스 및 해결 관련 정보를 이해하기 위해 탐지 결과의 전체 세부 정보를 검색합니다.
  • 보안 결과 분류하기: 탐지 결과에 대한 Jira 이슈, ServiceNow 티켓 또는 Case Management 케이스를 생성합니다. 탐지 결과를 팀원에게 할당하거나 오탐 및 허용된 위험에 대한 알림을 해제합니다.
  • 신호와 탐지 결과의 상관관계 분석하기: 활성 보안 신호와 미해결 탐지 결과를 교차 분석하여, 경고가 알려진 보안 태세 이슈와 관련이 있는지 확인합니다.
  • 탐지 규칙 검사 및 관리: 탐지 규칙을 나열, 검색, 생성, 업데이트 및 삭제하여 신호를 생성하는 로직을 파악하고 관리합니다.
  • 억제 관리하기: 억제를 생성, 업데이트 및 삭제하여 규칙 전체를 비활성화하지 않고도 특정 조건에서 과도하게 발생하는 규칙을 일시적으로 무시할 수 있습니다.
  • App & API Protection으로 공격에 대응: 차단 목록에 있는 IP, 사용자 및 사용자 에이전트를 차단하거나 차단 해제하고, 허용 목록 제외 필터를 사용해 오탐을 억제하며, 사용자 지정 WAF 규칙을 생성, 업데이트 또는 삭제하여 특정 서비스나 엔드포인트를 보호합니다.
  • AI 에이전트를 사용하여 취약점 해결하기: 코드 위치 및 수정 지침을 포함한 라이브러리 취약점 탐지 결과를 가져오고 이를 AI 에이전트에 전달하여 코드베이스에서 직접 패치를 적용합니다.
  • IoC 조사: 위협 인텔리전스 피드와 일치하는 IP 주소, 도메인, URL 및 파일 해시를 검색하고 가져옵니다. 개별 지표를 검토하고 분류 상태를 업데이트합니다.
  • IaC 사용자 지정 규칙 작성: 자연어 설명을 기반으로 Rego 기반 인프라(IaC) 사용자 지정 규칙을 생성, 검증 및 게시합니다.

빠른 시작

기본적으로 security 도구 세트는 활성화되어 있지 않습니다. URL에 파라미터를 추가하여 보안 도구가 AI 클라이언트와 상호작용할 수 있도록 활성화할 수 있습니다.

  1. Datadog MCP 서버를 설정합니다.
  2. Datadog MCP 서버에 연결할 때security를 toolsets 파라미터에 추가하세요. 예를 들어 Datadog 사이트()에는 다음을 사용하세요.
    https://mcp./v1/mcp?toolsets=core,security
    
?toolsets=security must be in the URL. Otherwise, security tools are not available to your AI client, even if the MCP Server is otherwise connected and working.

Available tools

The security toolset exposes the following tools to your AI client. Each tool performs a specific action on your security data. When you ask a question in natural language, your AI client calls these tools on your behalf to retrieve the information it needs. For general information on how to use MCP tools, see the Datadog MCP Server Overview.

Security Signals

get_datadog_security_signals_schema
Returns the available fields and their types for security signals. Signal types map to @workflow.rule.type values such as Log Detection, Application Security, and Workload Security.
Permissions required: Security Signals Read
search_datadog_security_signals
Searches and retrieves security signals from Datadog, including Cloud SIEM signals, App & API Protection signals, and Workload Protection signals. Use this to surface and investigate suspicious activity.
Permissions required: Security Signals Read
analyze_datadog_security_signals
Analyzes security signals using SQL for aggregations, grouping, and trend analysis. Use this for counts, top-N breakdowns, and time-based questions. To list signals or retrieve a single signal, use search_datadog_security_signals or get_datadog_security_signal instead. Call get_datadog_security_signals_schema first to discover queryable fields.
Permissions required: Security Signals Read, Timeseries
get_datadog_security_signal
Retrieves the full details of a single security signal by ID, including attributes, rule information, triage state, tags, and case correlations. Use search_datadog_security_signals to find signal IDs first.
Permissions required: Security Signals Read
update_datadog_security_signals_triage
Updates the triage state or assignee of one or more security signals in bulk (up to 500 signals). Accepts either a list of signal IDs or a filter query matching all signals to update.
Permissions required: Security Signals Write

IoC Explorer

search_datadog_security_ioc_indicators
Lists IoC Explorer indicators (IP addresses, domains, URLs, and file hashes) matched against threat intelligence feeds. Use this to surface and investigate indicators of compromise in your environment.
Permissions required: Security Signals Read
get_datadog_security_ioc_indicator
Retrieves full details for a single IoC Explorer indicator by value, including score, category, Autonomous System (AS) information, GeoIP data, log sources, and signal counts.
Permissions required: Security Signals Read
get_datadog_security_ioc_schema
Returns available filterable fields and their values for IoC Explorer. Omit filter to list available fields; supply filter to get values with counts. Use query to scope results to a subset of indicators.
Permissions required: Security Signals Read
update_datadog_security_ioc_indicator_triage
Sets the triage state of an IoC Explorer indicator to mark it as reviewed or not reviewed.
Permissions required: Security Signals Write

Security Findings

get_datadog_security_findings_schema
Returns the available fields and their types for security findings. Call this before using analyze_datadog_security_findings to discover which fields you can filter and group by. Supports filtering by finding type.
Permissions required: Security Monitoring Findings Read
analyze_datadog_security_findings
Primary tool for analyzing security findings using SQL. Queries live data from the last 24 hours with support for aggregations, filtering, and grouping. Call get_datadog_security_findings_schema first to discover available fields.
Permissions required: Security Monitoring Findings Read, Timeseries
search_datadog_security_findings
Retrieves full security finding objects. Use this when you need complete finding details or when SQL-based analysis is not sufficient. Prefer analyze_datadog_security_findings for most analysis tasks.
Permissions required: Security Monitoring Findings Read
get_datadog_security_findings_ticket_suggestions
Returns ranked project suggestions for ticketing security findings. Shows available Case Management, Jira, Linear, and ServiceNow projects with usage data. Call this before create_datadog_security_findings_ticket to discover which project to use.
Permissions required: Security Monitoring Findings Read, Cases Read
create_datadog_security_findings_ticket
Creates a Case Management case, Jira issue, Linear issue, or ServiceNow ticket for security findings. Requires specific finding IDs and a project ID. Use get_datadog_security_findings_ticket_suggestions first to discover available projects.
Permissions required: Security Monitoring Findings Write, Cases Read, Cases Write
detach_datadog_security_findings_ticket
Detaches security findings from their linked case or ticket. Since Jira and ServiceNow tickets are linked through Case Management, detaching the case also detaches any downstream ticket.
Permissions required: Security Monitoring Findings Write, Cases Write
mute_datadog_security_findings
Mutes or unmutes security findings to suppress them from alerts and dashboards. Requires a mute reason (PENDING_FIX, FALSE_POSITIVE, ACCEPTED_RISK, or OTHER) and supports an optional description and expiration date.
Permissions required: Security Monitoring Findings Write
assign_datadog_security_findings
Assigns or unassigns security findings to a user. Assignment cascades to any linked cases. Omit the assignee ID to unassign.
Permissions required: Security Monitoring Findings Write
list_datadog_security_findings_automation_rules
Lists security findings automation rules of a given type (mute, due_date, ticket_creation, or severity_modifier).
Permissions required: Security Pipelines Read
create_datadog_security_findings_automation_rule
Creates a security findings automation rule. Choose a rule_type: mute (suppress findings), due_date (set remediation deadlines), severity_modifier (adjust finding severity), or ticket_creation (auto-create Jira or Case Management tickets).
Permissions required: Security Pipelines Write, Security Monitoring Findings Read
update_datadog_security_findings_automation_rule
Updates an existing automation rule. Supports partial updates, so only the provided fields are changed. Use it to enable or disable rules, rename them, adjust filters, or change action parameters.
Permissions required: Security Pipelines Write
delete_datadog_security_findings_automation_rule
Permanently deletes a security findings automation rule by ID.
Permissions required: Security Pipelines Write
reorder_datadog_security_findings_automation_rules
Moves an automation rule up or down in the list. Rules are applied in order, so a rule’s position sets its priority.
Permissions required: Security Pipelines Write

Detection Rules

get_datadog_security_detection_rules_schema
Returns the authoring reference and schema for detection rules. Covers supported rule types, detection methods, query syntax, tag conventions, and field names that can be used as search facets. Use this before authoring or querying detection rules. Currently supported rule types: log detection and API security.
Permissions required: Security Monitoring Rules Read
get_datadog_security_detection_rules
Retrieves security detection rules. Supports two modes: provide rule_id to get the full definition of a single rule by ID, or omit rule_id to list rules (optionally filtered with query and token-limited with max_tokens). The two modes are mutually exclusive.
Permissions required: Security Monitoring Rules Read
create_datadog_security_detection_rule
Creates a new detection rule. Call get_datadog_security_detection_rules_schema first to fetch the required payload grammar, then supply a complete rule payload. On success, returns the full rule including its server-assigned ID.
Permissions required: Security Monitoring Rules Write
update_datadog_security_detection_rule
Updates an existing custom detection rule by replacing it entirely. Use this to enable or disable a rule, change thresholds, add cases, and more. Call get_datadog_security_detection_rules first to fetch the current rule body, modify the fields you need to change, and submit the full updated object. Cannot update Datadog-shipped default rules. On success, returns the full updated rule.
Permissions required: Security Monitoring Rules Write
delete_datadog_security_detection_rules
Deletes one or more custom detection rules by ID. Only custom (non-default) rules can be deleted. Each rule is authorized individually; rules that cannot be deleted appear in failed_rules without aborting the batch. Returns deleted_rules and failed_rules.
Permissions required: Security Monitoring Rules Write

Suppressions

get_datadog_security_suppressions
Retrieves security monitoring suppressions. Supports three modes: list all suppressions, get a single suppression by ID, or get suppressions affecting a specific detection rule. Suppressions prevent detection rules from generating signals for matching conditions.
Permissions required: Security Monitoring Suppressions Read
create_datadog_security_suppression
Creates a new suppression rule that prevents a detection rule from generating signals matching specific conditions. At least one of suppression_query or data_exclusion_query must be provided.
Permissions required: Security Monitoring Suppressions Write
update_datadog_security_suppression
Updates an existing suppression rule. Only changes provided fields. Providing version enables optimistic concurrency control to prevent overwriting concurrent edits.
Permissions required: Security Monitoring Suppressions Write
delete_datadog_security_suppression
Deletes a suppression rule.
Permissions required: Security Monitoring Suppressions Write

App & API Protection

get_datadog_security_trace_passlist
Returns all WAF exclusion filter (passlist) entries for the organization to review existing suppressions.
Permissions required: Application Security Management Protect Read
upsert_datadog_security_trace_passlist
Creates or updates a WAF exclusion filter (passlist) entry to suppress noisy rules on a specific service or endpoint.
Permissions required: Application Security Management Protect Write
delete_datadog_security_trace_passlist
Deletes an existing WAF exclusion filter (passlist) entry.
Permissions required: Application Security Management Protect Write
get_datadog_security_aap_denylist
Lists blocked IPs, users, and user agents (denylist entries), with optional filtering.
Permissions required: Application Security Management Protect Read
upsert_datadog_security_aap_denylist
Adds or updates a denylist block for an IP, user, or user agent with an expiration.
Permissions required: Application Security Management Protect Write
unblock_datadog_security_aap_denylist
Unblocks a previously denylisted entity by setting its expiration in the past.
Permissions required: Application Security Management Protect Write
get_datadog_security_aap_custom_rules
Retrieves one App & API Protection (AAP) custom WAF rule by ID or lists custom rules. Supports filtering by category, status, service, and environment.
Permissions required: Application Security Management Protect Read
upsert_datadog_security_aap_custom_rule
Creates or updates an AAP custom WAF rule in the attack attempt or business logic category. New rules cannot block traffic: create the rule in monitoring mode, then update it to blocking mode after confirming its matches.
Permissions required: Application Security Management Protect Write
delete_datadog_security_aap_custom_rule
Permanently deletes an AAP custom WAF rule by ID.
Permissions required: Application Security Management Protect Write
get_datadog_security_aap_blocking_config
Retrieves the organization-wide AAP blocking and denylist enforcement settings.
Permissions required: Application Security Management Protect Read

Infrastructure as Code custom rules

get_datadog_security_iac_custom_rules
Retrieves one Infrastructure as Code (IaC) custom rule by ID or lists the custom rules in your organization. Supports filtering by platform, provider, published state, or a text query. Listing returns the full custom ruleset without pagination.
Permissions required: Vulnerability Management Read
get_datadog_security_iac_custom_rules_schema
Returns the schema for IaC custom rules: allowed platforms, categories, severities, the rule ID format, and the fields each write tool accepts. Call this tool before generating, validating, or creating a rule.
Permissions required: Vulnerability Management Read
generate_datadog_security_iac_custom_rule
Generates a Rego IaC custom rule from a natural-language description and validates it with the scanner. Does not save the rule.
Permissions required: Vulnerability Management Write
validate_datadog_security_iac_custom_rule
Checks that the Rego for an IaC custom rule compiles. When a sample file is provided, also evaluates the rule against it and requires at least one finding. Does not save the rule.
Permissions required: Vulnerability Management Write
create_datadog_security_iac_custom_rule
Creates a draft IaC custom rule. Rules are always created unpublished. To activate a rule for scans, publish it with publish_datadog_security_iac_custom_rule.
Permissions required: Vulnerability Management Write
update_datadog_security_iac_custom_rule
Creates a new revision of a draft or published IaC custom rule. Omitted fields keep their current values, including the published state. Can also publish or unpublish the rule.
Permissions required: Vulnerability Management Read and Vulnerability Management Write
publish_datadog_security_iac_custom_rule
Publishes a draft IaC custom rule so it becomes active for scans. To unpublish it later, use update_datadog_security_iac_custom_rule.
Permissions required: Vulnerability Management Read and Vulnerability Management Write
delete_datadog_security_iac_custom_rule
Permanently deletes an IaC custom rule by ID. This action cannot be undone.
Permissions required: Vulnerability Management Write

Further reading