Claude Datadog connectorWhat Claude can do in your Datadog account.
The Claude Datadog connector exposes 182 tools. 97 of them read telemetry and settings, 20 change something in your account, and 65 are described nowhere under their listed name. Below: what Claude investigates, what it can build or delete, and which permissions decide it.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for the engineer on call
During an incident, answers are spread across logs, traces, monitors and dashboards. With the connector, you ask Claude in plain language: it searches logs, pulls the trace, checks which monitors fire and what changed, then summarizes. It can also draft a monitor, update a dashboard or run a workflow, each behind a confirmation.
Find the cause faster. search_datadog_logs pulls the errors of a service, get_datadog_trace opens the slow request, and search_datadog_events shows the deployment that came just before.
Close monitoring gaps. get_monitor_coverage lists the signals no monitor watches, and create_datadog_monitor drafts one that stays silent until you publish it in Datadog.
Understand a slow database. find_datadog_database_instances locates the instance, get_datadog_database_query_performance gives the numbers, and optimize_datadog_database_query suggests rewrites without applying them.
Now what the connector does not do. It cannot give you more than your own Datadog roles allow, and a read-only user's write call is rejected. It is not available on GovCloud sites. And 65 names on the directory sheet do not match any entry in Datadog's current tools reference, which Datadog says is changing fast. Nothing runs on its own either: alerting on an event is a monitor's job, and the Datadog Make integration page covers automation.
The vocabulary in one minute
Five words you will meet while plugging Datadog into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Datadog into Claude in three steps
- 01
Find Datadog in Claude
In Claude's settings, open Customize, then Connectors, and look for Datadog in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Datadog in the window that Datadog opens itself. If the link ever breaks later on, use Disconnect and then plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Datadog, not to Claude, and it is what decides what the access covers. You can also withdraw that access later from your Datadog account.
The 182 tools, sorted by what they do
Datadog gives Claude 182 tools: 97 that read your account, 20 that change something in it, and 65 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes under its listed name. Tool names stay exactly as Claude shows them.
- 97 read
- 20 write
- 65 not documented
What Claude reads (97)
97 toolsNinety-seven tools that search, analyze or describe telemetry and settings without altering them.
search_datadog_logs
Searches your logs with filters such as time range, query, service, host or storage tier, and returns the matching log details. Datadog's reference ties search_datadog_logs to these permissions: Logs Read Data and Logs Read Index Data.
analyze_datadog_logs
Runs SQL-style analysis over your logs for counts, aggregations and numbers, the statistical side of log work rather than reading lines one by one. Datadog's reference ties analyze_datadog_logs to these permissions: Logs Read Data and Logs Read Index Data and Timeseries.
search_datadog_events
Looks through Datadog events such as monitor alerts, deployment notices, infrastructure events, security findings and service status notices. Datadog's reference ties search_datadog_events to these permissions: Events and Timeseries.
get_datadog_metric
Queries historical or real-time metric data with custom queries and aggregations, including cloud cost figures when you have that permission. Datadog's reference ties get_datadog_metric to these permissions: Cloud Cost Management Read or Metrics or Timeseries.
search_datadog_metrics
Lists the metrics available in your account, with filters and metadata, so Claude picks the right name before querying. Datadog's reference ties search_datadog_metrics to these permissions: Metrics.
get_datadog_metric_context
Retrieves what surrounds a metric: metadata, available tags and tag values that can be used to filter or group it. Datadog's reference ties get_datadog_metric_context to these permissions: Cloud Cost Management Read or Metrics.
search_datadog_monitors
Returns information about your monitors, including their status, thresholds and alert conditions. Datadog's reference ties search_datadog_monitors to these permissions: Monitors Read.
get_datadog_trace
Fetches a complete trace from APM using its trace ID, with spans and timing, so Claude can walk through one slow request. Datadog's reference ties get_datadog_trace to these permissions: APM Read.
search_datadog_spans
Finds spans from APM traces using filters such as service, time or resource, the building blocks behind each request. Datadog's reference ties search_datadog_spans to these permissions: APM Read.
aggregate_spans
Computes counts, sums, averages, minimums, maximums, cardinality and percentiles over APM spans, grouped by service or resource, or as a timeseries. Datadog's reference ties aggregate_spans to these permissions: APM Read.
search_datadog_incidents
Lists your Datadog incidents with their state, severity and metadata. Datadog's reference ties search_datadog_incidents to these permissions: Incidents Read.
get_datadog_incident
Opens a single incident in detail, so Claude can tell you where it stands. Datadog's reference ties get_datadog_incident to these permissions: Incidents Read.
search_datadog_hosts
Lists and describes the hosts Datadog monitors, with filtering and search. Datadog's reference ties search_datadog_hosts to these permissions: Hosts Read and Timeseries.
search_datadog_dashboards
Lists available dashboards and their key details, a way to find the right one by topic or team. Datadog's reference ties search_datadog_dashboards to these permissions: Dashboards Read and User Access Read.
get_datadog_notebook
Retrieves one notebook by ID, with its name, status and author. Datadog's reference ties get_datadog_notebook to these permissions: Notebooks Read.
search_datadog_notebooks
Searches notebooks with filters on author, tags and content. Datadog's reference ties search_datadog_notebooks to these permissions: Notebooks Read.
search_datadog_rum_events
Searches Real User Monitoring events with Datadog's query syntax, the view of what real visitors experienced. Datadog's reference ties search_datadog_rum_events to these permissions: RUM Apps Read.
aggregate_rum_events
Turns RUM events into counts, sums, averages, percentiles and more, with grouping, for trends rather than single sessions. Datadog's reference ties aggregate_rum_events to these permissions: RUM Apps Read.
search_datadog_slos
Searches your service level objectives by name, tags or type, with query syntax to filter by service or team. Datadog's reference ties search_datadog_slos to these permissions: SLOs Read.
get_monitor_coverage
Finds monitoring gaps for services or hosts: which signals, such as error rate, latency or request rate, existing monitors cover and which are missing. Datadog's reference ties get_monitor_coverage to these permissions: Monitors Read.
search_datadog_database_plans
Searches Database Monitoring execution plans, which show how the database engine runs a query: index use, join strategy and cost estimates. Datadog's reference ties search_datadog_database_plans to these permissions: Database Monitoring Read.
search_datadog_database_samples
Searches query samples, individual executions with their performance figures, to spot slow queries and activity patterns. Datadog's reference ties search_datadog_database_samples to these permissions: Database Monitoring Read.
search_datadog_error_tracking_issues
Searches Error Tracking issues across RUM, logs and traces, the grouped view of recurring errors. Datadog's reference ties search_datadog_error_tracking_issues to these permissions: Error Tracking Read.
get_datadog_error_tracking_issue
Opens one Error Tracking issue with its full detail, the context a developer needs. Datadog's reference ties get_datadog_error_tracking_issue to these permissions: Cases Read and Error Tracking Read.
search_ndm_devices
Searches network devices such as routers, switches and firewalls watched by Network Device Monitoring. Datadog's reference ties search_ndm_devices to these permissions: NDM Read.
get_ndm_device
Describes one network device from its device ID, with the details Datadog holds. Datadog's reference ties get_ndm_device to these permissions: NDM Read.
search_ndm_interfaces
Lists all the network interfaces of a given device. Datadog's reference ties search_ndm_interfaces to these permissions: NDM Read.
analyze_cloud_network_monitoring
Investigates network-level problems from Cloud Network Monitoring flow data, spotting anomalies such as high retransmission rates. Datadog's reference ties analyze_cloud_network_monitoring to these permissions: Network Connections Read.
browser_onboarding
Guides you through onboarding Browser RUM, the real-user monitoring of a website, step by step in the conversation. Datadog's reference ties browser_onboarding to these permissions: RUM Apps Read.
devices_onboarding
Walks you through bringing devices under Datadog monitoring. Datadog's reference ties devices_onboarding to these permissions: RUM Apps Read.
kubernetes_onboarding
Explains, step by step, how to connect Kubernetes clusters to Datadog. Datadog's reference ties kubernetes_onboarding to these permissions: None.
llm_observability_onboarding
Helps you set up Agent Observability, Datadog's monitoring for AI applications.
serverless_onboarding
Coaches you on onboarding serverless applications, including AWS Lambda functions and GCP Cloud Run. Datadog's reference ties serverless_onboarding to these permissions: None.
source_map_uploads
Shows you how to upload source maps, so RUM errors point to your original source code.
test_optimization_onboarding
Leads you through onboarding Test Optimization, Datadog's view of your automated tests. Datadog's reference ties test_optimization_onboarding to these permissions: None.
search_datadog_security_signals
Searches security signals from Cloud SIEM, App and API Protection and Workload Protection. Datadog's reference ties search_datadog_security_signals to these permissions: Security Signals Read.
search_datadog_ci_pipeline_events
Searches continuous integration events with filters and returns their details. Datadog's reference ties search_datadog_ci_pipeline_events to these permissions: CI Visibility Read.
aggregate_datadog_ci_pipeline_events
Aggregates CI pipeline events into statistics, metrics and grouped analytics. Datadog's reference ties aggregate_datadog_ci_pipeline_events to these permissions: CI Visibility Read.
get_datadog_flaky_tests
Searches Test Optimization for flaky tests and returns triage details: failure rate, category, owners, history and CI impact. Datadog's reference ties get_datadog_flaky_tests to these permissions: Test Optimization Read.
search_datadog_test_events
Looks up Test Optimization test events with filters and returns their details. Datadog's reference ties search_datadog_test_events to these permissions: Test Optimization Read.
aggregate_datadog_test_events
Aggregates Test Optimization events to measure reliability and performance trends, with group-by facets and configurable test levels. Datadog's reference ties aggregate_datadog_test_events to these permissions: Test Optimization Read.
get_datadog_code_coverage_branch_summary
Fetches code coverage summary figures for a repository branch, with total and patch coverage plus service and code owner breakdowns. Datadog's reference ties get_datadog_code_coverage_branch_summary to these permissions: Code Coverage read.
get_datadog_code_coverage_commit_summary
Gives the same coverage summary for one commit: total coverage, patch coverage and breakdowns by service and code owner. Datadog's reference ties get_datadog_code_coverage_commit_summary to these permissions: Code Coverage read.
get_synthetics_tests
Searches your Synthetic HTTP API tests, the scripted checks that probe endpoints from the outside. Datadog's reference ties get_synthetics_tests to these permissions: Synthetics Read.
list_datadog_workflows
Lists and searches Workflow Automation workflows by name, creator, handle, tag or trigger type, with metadata and optionally the full specification. Datadog's reference ties list_datadog_workflows to these permissions: Workflows Read.
get_datadog_workflow
Retrieves a workflow by ID with its metadata and complete specification, returning a saved draft when one exists. Datadog's reference ties get_datadog_workflow to these permissions: Workflows Read.
get_datadog_workflow_instance
Retrieves a lightweight summary of a workflow run, with an option to include the detailed execution record. Datadog's reference ties get_datadog_workflow_instance to these permissions: Workflows Read.
analyze_datadog_security_signals
Analyzes security signals with SQL-style queries for counts, top lists and breakdowns over time. Datadog's reference ties analyze_datadog_security_signals to these permissions: Security Signals Read and Timeseries.
get_datadog_security_signal
Retrieves the full details of one security signal: attributes, rule information, triage state, tags and case links. Datadog's reference ties get_datadog_security_signal to these permissions: Security Signals Read.
get_datadog_security_signals_schema
Returns the fields available on security signals and their types, so queries use valid names. Datadog's reference ties get_datadog_security_signals_schema to these permissions: Security Signals Read.
get_datadog_security_detection_rules_schema
Returns the authoring reference for detection rules: supported rule types, detection methods, query syntax, tag conventions and valid search facets. Datadog's reference ties get_datadog_security_detection_rules_schema to these permissions: Security Monitoring Rules Read.
get_datadog_security_suppressions
Retrieves security suppressions: the full list, one by ID, or those affecting a given detection rule. Datadog's reference ties get_datadog_security_suppressions to these permissions: Security Monitoring Suppressions Read.
ddsql_create_link
Generates a link to the DDSQL Editor in the Datadog interface with a given query already filled in, so you can open it yourself.
ddsql_get_spec
Gets a compact description of what DDSQL supports: SQL functions, keywords and how it differs from standard PostgreSQL.
ddsql_run_query
Runs a DDSQL query and returns the results, across infrastructure resources, logs, metrics, RUM, spans and other Datadog sources.
ddsql_schema_get_table_columns
Gets the columns of a DDSQL table from its schema metadata.
ddsql_schema_search_tables
Searches DDSQL datasets and returns tables, including reference tables, along with the metrics you can query.
ddsql_schema_search_unstructured_fields
Searches and ranks fields for unstructured sources such as logs, RUM and spans, sorted by how often they appear.
ddsql_read_saved_query
Gets a saved DDSQL query by ID with its name, SQL text, columns, description and author.
ddsql_search_saved_queries
Searches saved DDSQL queries by name or description, most recent first, with pagination; several words must all match.
get_datadog_dashboard
Retrieves a dashboard by ID with its title, description, tags and full widget definitions. Datadog's reference ties get_datadog_dashboard to these permissions: Dashboards Read and User Access Read.
ask_widget_expert
Asks a Datadog widget expert a targeted question about widget configuration, schemas, query syntax, fields or pitfalls. Datadog's reference ties ask_widget_expert to these permissions: Dashboards Read or Dashboards Write or Notebooks Read.
get_widget_reference
Returns schemas and building instructions for dashboard widget types, including query patterns, formula syntax and common pitfalls. Datadog's reference ties get_widget_reference to these permissions: Dashboards Read or Dashboards Write or Notebooks Read.
validate_dashboard_widget
Validates a widget definition against the dashboard schema, catching errors before anything reaches a dashboard. Datadog's reference ties validate_dashboard_widget to these permissions: Dashboards Read or Dashboards Write or Notebooks Read.
search_datadog_k8s_resources
Searches Kubernetes resources such as deployments, pods and nodes across all clusters, with tags and parent resources, without local cluster access. Datadog's reference ties search_datadog_k8s_resources to these permissions: Hosts Read and Teams Read.
describe_datadog_k8s_resource
Gets detailed information about one Kubernetes resource, such as CPU and memory requests and limits, plus optional labels, history and a link to the Kubernetes Explorer. Datadog's reference ties describe_datadog_k8s_resource to these permissions: Hosts Read.
get_datadog_k8s_manifest
Retrieves the YAML manifest of a Kubernetes resource, with an option to extract a subtree or drop status fields to keep it short. Datadog's reference ties get_datadog_k8s_manifest to these permissions: Hosts Read.
list_reference_tables
Browses the Reference Tables in your organization, with filtering by name and sorting.
list_reference_table_rows or get_reference_table_rows.get_reference_table_rows
Retrieves specific rows of a reference table from their primary key values.
list_reference_tables first to get the table ID and schema.list_reference_table_rows
Lists every row of a reference table, with optional filtering and pagination.
find_datadog_database_instances
Discovers and ranks database instances for an investigation, from a trace or span ID, tags or both, and assesses their health. Datadog's reference ties find_datadog_database_instances to these permissions: Database Monitoring Read.
get_datadog_database_calling_services
Identifies the upstream services and resources that issue queries to a database, linking database activity to application traces. Datadog's reference ties get_datadog_database_calling_services to these permissions: Database Monitoring Read.
get_datadog_database_explain_plans
Retrieves PostgreSQL explain plans for a query signature over a time frame, simplified and sorted by cost. Datadog's reference ties get_datadog_database_explain_plans to these permissions: Database Monitoring Read.
get_datadog_database_health_signals
Runs health checks that surface PostgreSQL issues such as CPU saturation, restarts, query latency and blocking, comparing a problem window with a baseline. Datadog's reference ties get_datadog_database_health_signals to these permissions: Database Monitoring Read.
get_datadog_database_query_performance
Analyzes one PostgreSQL query's performance: throughput, latency, rows per run, cache hit ratio, input and output, waits and transaction time, overall and over time. Datadog's reference ties get_datadog_database_query_performance to these permissions: Database Monitoring Read.
get_datadog_database_query_statement
Retrieves the SQL text behind a query signature, turning an opaque hash into readable SQL. Datadog's reference ties get_datadog_database_query_statement to these permissions: Database Monitoring Read.
get_datadog_database_recommendations
Retrieves live recommendations for a database, query, table, host or index, with status, severity and the affected scope. Datadog's reference ties get_datadog_database_recommendations to these permissions: Database Monitoring Read.
get_datadog_database_schemas
Fetches schema definitions, columns, indexes, foreign keys and partitions, for one or more database objects. Datadog's reference ties get_datadog_database_schemas to these permissions: Database Monitoring Read.
optimize_datadog_database_query
Analyzes a PostgreSQL query with deterministic rules and returns suggested rewrites, anti-patterns, missing index ideas and idle-in-transaction impact. Datadog's reference ties optimize_datadog_database_query to these permissions: Database Monitoring Read.
get_profiling_field_values
Returns the values of one frame or context field found through the profiling fields tool, sorted by frequency. Datadog's reference ties get_profiling_field_values to these permissions: Continuous Profiler Read.
get_profiling_fields
Discovers the frame and context fields you can use to group or filter profiling timeseries, scoped by sample type. Datadog's reference ties get_profiling_fields to these permissions: Continuous Profiler Read.
get_profiling_profile_types
Returns the profile types and families available for a query context or a trace, the first step to know what can be explored. Datadog's reference ties get_profiling_profile_types to these permissions: Continuous Profiler Read.
get_profiling_runtime_ids
Returns the individual profiled processes or containers in scope, by default the single top one by CPU. Datadog's reference ties get_profiling_runtime_ids to these permissions: Continuous Profiler Read.
get_profiling_service_insights
Returns pre-computed insights for a service: a summary, affected methods, packages and processes, and recommended next steps. Datadog's reference ties get_profiling_service_insights to these permissions: Continuous Profiler Read.
get_profiling_services
Lists the services that have profiling and their profiling families. Datadog's reference ties get_profiling_services to these permissions: Continuous Profiler Read.
get_profiling_tag_names
Discovers tag names such as service, host, env or version for filtering profiling data, up to 50 results sorted by relevance. Datadog's reference ties get_profiling_tag_names to these permissions: Continuous Profiler Read.
get_profiling_tag_values
Gives the values of one profiling tag, for example every service name, up to 50 sorted by frequency. Datadog's reference ties get_profiling_tag_values to these permissions: Continuous Profiler Read.
get_profiling_timeseries
Returns profiling data aggregated as timeseries, suited to trends, comparisons across services and spotting regressions. Datadog's reference ties get_profiling_timeseries to these permissions: Continuous Profiler Read.
explore_profiling_call_graph
Returns a caller-to-callee view of hot functions for a profile type, by default the top 20 nodes for one service. Datadog's reference ties explore_profiling_call_graph to these permissions: Continuous Profiler Read.
explore_profiling_flame_graph
Returns the top stack traces by contribution for a profile type, with filters on frame, endpoint or attribute. Datadog's reference ties explore_profiling_flame_graph to these permissions: Continuous Profiler Read.
explore_profiling_timeline
Returns a timeline of threads, garbage collection and other lanes with CPU and input/output activity, with a critical-path mode for Go traces. Datadog's reference ties explore_profiling_timeline to these permissions: Continuous Profiler Read.
aggregate_dora_deployments
Returns DORA metrics, deployment frequency, lead time, failure rate of deployments and recovery time, for a service, team or repository. Datadog's reference ties aggregate_dora_deployments to these permissions: Timeseries.
search_dora_deployments
Searches DORA deployment events with filters, or fetches the full details of one deployment. Datadog's reference ties search_dora_deployments to these permissions: DORA Metrics Read.
get_datadog_flaky_tests_management_policies
Retrieves the flaky test management policies of a repository: quarantine windows, branch rules, failure thresholds, disable policies and retries. Datadog's reference ties get_datadog_flaky_tests_management_policies to these permissions: Test Optimization Read.
get_datadog_test_optimization_settings
Retrieves which Test Optimization features are on for a service, such as Test Impact Analysis, early flake detection, auto retries or PR comments. Datadog's reference ties get_datadog_test_optimization_settings to these permissions: Test Optimization Read.
get_widget
Retrieves Datadog data, metrics, traces, logs and more, and shows it as an interactive chart in the conversation, from a dashboard, a definition or a URL. Datadog's reference ties get_widget to these permissions: Dashboards Read or Timeseries or Monitors Read or APM Read or RUM Apps Read.
visualize_tabular_data
Renders tabular data as an interactive sunburst, treemap or top list, after Claude has aggregated the numbers. Datadog's reference ties visualize_tabular_data to these permissions: No specific permissions required..
What Claude changes (20)
20 toolsTwenty tools that act on notebooks, monitors, tests, rules, dashboards, tables or workflows. Only one has a sourced confirmation; for the others the general rule below applies.
create_datadog_notebook
Approval: see the ruleCreates a new Datadog notebook, the shared document where teams gather graphs and notes during an investigation. Datadog's reference ties create_datadog_notebook to these permissions: Notebooks Read and Notebooks Write.
create_datadog_notebook, so the general approvals rule applies.edit_datadog_notebook
Approval: see the ruleEdits an existing notebook, so findings from the conversation can be added to a shared investigation. Datadog's reference ties edit_datadog_notebook to these permissions: Notebooks Read and Notebooks Write.
edit_datadog_notebook, so the general approvals rule covers it.create_datadog_monitor
Approval: see the ruleCreates a monitor in draft mode: it sends no notifications and gets priority 5, and you publish it later in the Datadog interface. Datadog's reference ties create_datadog_monitor to these permissions: Monitors Write.
create_datadog_monitor is documented; the general approvals rule applies.edit_synthetics_tests
Approval: see the ruleEdits your Synthetic HTTP API tests, the scripted checks that probe endpoints. Datadog's reference ties edit_synthetics_tests to these permissions: Synthetics Global Variable Read and Synthetics Read and Synthetics Write.
edit_synthetics_tests, so the general approvals rule governs it.synthetics_test_wizard
Approval: see the rulePreviews and creates Synthetic HTTP API tests, a guided way to set up a new external check. Datadog's reference ties synthetics_test_wizard to these permissions: Synthetics Global Variable Read and Synthetics Read and Synthetics Write.
synthetics_test_wizard; the general approvals rule is what applies.execute_datadog_workflow
Approval: see the ruleStarts a new run of a workflow that has an agent trigger, using the saved draft when one exists. Datadog's reference ties execute_datadog_workflow to these permissions: Workflows Run.
execute_datadog_workflow, so the general approvals rule applies.create_datadog_security_detection_rule
Approval: see the ruleAdds a new security detection rule from a complete payload, after Claude has checked the rule grammar. Datadog's reference ties create_datadog_security_detection_rule to these permissions: Security Monitoring Rules Write.
create_datadog_security_detection_rule, so the general approvals rule covers it.update_datadog_security_detection_rule
Approval: see the ruleUpdates an existing custom detection rule by replacing it entirely with a new version. Datadog's reference ties update_datadog_security_detection_rule to these permissions: Security Monitoring Rules Write.
update_datadog_security_detection_rule is documented; the general approvals rule applies.delete_datadog_security_detection_rules
Approval: see the ruleDeletes one or more custom detection rules by ID; each rule is authorized on its own and failures do not stop the batch. Datadog's reference ties delete_datadog_security_detection_rules to these permissions: Security Monitoring Rules Write.
delete_datadog_security_detection_rules, so the general approvals rule governs it.create_datadog_security_suppression
Approval: see the ruleCreates a suppression that stops a detection rule from generating signals under chosen conditions. Datadog's reference ties create_datadog_security_suppression to these permissions: Security Monitoring Suppressions Write.
create_datadog_security_suppression; the general approvals rule is what applies.update_datadog_security_suppression
Approval: see the ruleRevises an existing suppression, changing only the fields provided, with an optional version check against concurrent edits. Datadog's reference ties update_datadog_security_suppression to these permissions: Security Monitoring Suppressions Write.
update_datadog_security_suppression, so the general approvals rule applies.delete_datadog_security_suppression
Approval: see the ruleDeletes a suppression rule, so the detection rule it covered produces signals again. Datadog's reference ties delete_datadog_security_suppression to these permissions: Security Monitoring Suppressions Write.
delete_datadog_security_suppression, so the general approvals rule covers it.update_datadog_security_signals_triage
Approval: see the ruleUpdates the triage state or assignee of security signals in bulk, up to 500 at once, from a list of IDs or a filter query. Datadog's reference ties update_datadog_security_signals_triage to these permissions: Security Signals Write.
update_datadog_security_signals_triage is documented; the general approvals rule applies.ddsql_upsert_saved_query
Approval: see the ruleCreates a saved DDSQL query or updates one by ID, keeping any name or SQL text you leave out.
ddsql_upsert_saved_query, so the general approvals rule governs it.upsert_datadog_dashboard
Approval: see the ruleCreates a dashboard, or updates one when given its ID, after Claude checks the widget formats. Datadog's reference ties upsert_datadog_dashboard to these permissions: Dashboards Read and Dashboards Write.
upsert_datadog_dashboard; the general approvals rule is what applies.delete_datadog_dashboard
Approval: see the rulePermanently deletes a dashboard by ID; Datadog states the action cannot be undone. Datadog's reference ties delete_datadog_dashboard to these permissions: Dashboards Read and Dashboards Write.
delete_datadog_dashboard, so the general approvals rule applies.create_reference_table
Approval: see the ruleSets up a new reference table, either empty or synced from a CSV file in cloud storage; only integer and string fields are supported.
create_reference_table, so the general approvals rule covers it.append_reference_table_rows
Approval: see the ruleAppends new rows to an existing reference table without touching existing data; each row needs every required field.
append_reference_table_rows is documented; the general approvals rule applies.update_datadog_flaky_test_states
Asks you firstSets flaky tests to quarantined, disabled, fixed or active; Datadog notes every state change is reversible. Datadog's reference ties update_datadog_flaky_test_states to these permissions: Test Optimization Write.
update_datadog_error_tracking_issue
Approval: see the ruleUpdates the state or assignee of an Error Tracking issue. Datadog's reference ties update_datadog_error_tracking_issue to these permissions: Cases Read, Cases Write, Error Tracking Read, and Error Tracking Write.
update_datadog_error_tracking_issue; the general approvals rule is what applies.Not documented (65)
65 toolsThe directory publishes these sixty-five names; Datadog's current reference documents none of them under that exact spelling. This page will not guess from a name.
aggregate_events
aggregate_events appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name aggregate_events, and no Claude help page describes it either. Guessing what aggregate_events does from its name would be invention, so this page leaves its role open.
aggregate_events, the general approvals rule is the only guidance that covers it.search_datadog_services
search_datadog_services appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_datadog_services, and no Claude help page describes it either. Guessing what search_datadog_services does from its name would be invention, so this page leaves its role open.
search_datadog_services, the general approvals rule is the only guidance that covers it.search_datadog_service_dependencies
search_datadog_service_dependencies appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_datadog_service_dependencies, and no Claude help page describes it either. Guessing what search_datadog_service_dependencies does from its name would be invention, so this page leaves its role open.
search_datadog_service_dependencies, the general approvals rule is the only guidance that covers it.submit_mcp_feedback
submit_mcp_feedback appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name submit_mcp_feedback, and no Claude help page describes it either. Guessing what submit_mcp_feedback does from its name would be invention, so this page leaves its role open.
submit_mcp_feedback, the general approvals rule is the only guidance that covers it.validate_monitor_definition
validate_monitor_definition appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name validate_monitor_definition, and no Claude help page describes it either. Guessing what validate_monitor_definition does from its name would be invention, so this page leaves its role open.
validate_monitor_definition, the general approvals rule is the only guidance that covers it.get_monitor_templates
get_monitor_templates appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_monitor_templates, and no Claude help page describes it either. Guessing what get_monitor_templates does from its name would be invention, so this page leaves its role open.
get_monitor_templates, the general approvals rule is the only guidance that covers it.monitor_groups_search
monitor_groups_search appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name monitor_groups_search, and no Claude help page describes it either. Guessing what monitor_groups_search does from its name would be invention, so this page leaves its role open.
monitor_groups_search, the general approvals rule is the only guidance that covers it.list-feature-flags
list-feature-flags appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list-feature-flags, and no Claude help page describes it either. Guessing what list-feature-flags does from its name would be invention, so this page leaves its role open.
list-feature-flags, the general approvals rule is the only guidance that covers it.get-feature-flag
get-feature-flag appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get-feature-flag, and no Claude help page describes it either. Guessing what get-feature-flag does from its name would be invention, so this page leaves its role open.
get-feature-flag, the general approvals rule is the only guidance that covers it.list-environments
list-environments appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list-environments, and no Claude help page describes it either. Guessing what list-environments does from its name would be invention, so this page leaves its role open.
list-environments, the general approvals rule is the only guidance that covers it.list-allocations-for-feature-flag
list-allocations-for-feature-flag appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list-allocations-for-feature-flag, and no Claude help page describes it either. Guessing what list-allocations-for-feature-flag does from its name would be invention, so this page leaves its role open.
list-allocations-for-feature-flag, the general approvals rule is the only guidance that covers it.create-feature-flag
create-feature-flag appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name create-feature-flag, and no Claude help page describes it either. Guessing what create-feature-flag does from its name would be invention, so this page leaves its role open.
create-feature-flag, the general approvals rule is the only guidance that covers it.check-flag-implementation
check-flag-implementation appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name check-flag-implementation, and no Claude help page describes it either. Guessing what check-flag-implementation does from its name would be invention, so this page leaves its role open.
check-flag-implementation, the general approvals rule is the only guidance that covers it.update-feature-flag-environment
update-feature-flag-environment appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name update-feature-flag-environment, and no Claude help page describes it either. Guessing what update-feature-flag-environment does from its name would be invention, so this page leaves its role open.
update-feature-flag-environment, the general approvals rule is the only guidance that covers it.sync-allocations-for-feature-flag-environment
sync-allocations-for-feature-flag-environment appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name sync-allocations-for-feature-flag-environment, and no Claude help page describes it either. Guessing what sync-allocations-for-feature-flag-environment does from its name would be invention, so this page leaves its role open.
sync-allocations-for-feature-flag-environment, the general approvals rule is the only guidance that covers it.get-canary-results
get-canary-results appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get-canary-results, and no Claude help page describes it either. Guessing what get-canary-results does from its name would be invention, so this page leaves its role open.
get-canary-results, the general approvals rule is the only guidance that covers it.list-guardrail-metrics
list-guardrail-metrics appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list-guardrail-metrics, and no Claude help page describes it either. Guessing what list-guardrail-metrics does from its name would be invention, so this page leaves its role open.
list-guardrail-metrics, the general approvals rule is the only guidance that covers it.get-guardrail-metric
get-guardrail-metric appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get-guardrail-metric, and no Claude help page describes it either. Guessing what get-guardrail-metric does from its name would be invention, so this page leaves its role open.
get-guardrail-metric, the general approvals rule is the only guidance that covers it.search_llmobs_spans
search_llmobs_spans appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_llmobs_spans, and no Claude help page describes it either. Guessing what search_llmobs_spans does from its name would be invention, so this page leaves its role open.
search_llmobs_spans, the general approvals rule is the only guidance that covers it.get_llmobs_trace
get_llmobs_trace appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_trace, and no Claude help page describes it either. Guessing what get_llmobs_trace does from its name would be invention, so this page leaves its role open.
get_llmobs_trace, the general approvals rule is the only guidance that covers it.get_llmobs_span_details
get_llmobs_span_details appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_span_details, and no Claude help page describes it either. Guessing what get_llmobs_span_details does from its name would be invention, so this page leaves its role open.
get_llmobs_span_details, the general approvals rule is the only guidance that covers it.get_llmobs_span_content
get_llmobs_span_content appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_span_content, and no Claude help page describes it either. Guessing what get_llmobs_span_content does from its name would be invention, so this page leaves its role open.
get_llmobs_span_content, the general approvals rule is the only guidance that covers it.find_llmobs_error_spans
find_llmobs_error_spans appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name find_llmobs_error_spans, and no Claude help page describes it either. Guessing what find_llmobs_error_spans does from its name would be invention, so this page leaves its role open.
find_llmobs_error_spans, the general approvals rule is the only guidance that covers it.expand_llmobs_spans
expand_llmobs_spans appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name expand_llmobs_spans, and no Claude help page describes it either. Guessing what expand_llmobs_spans does from its name would be invention, so this page leaves its role open.
expand_llmobs_spans, the general approvals rule is the only guidance that covers it.get_llmobs_agent_loop
get_llmobs_agent_loop appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_agent_loop, and no Claude help page describes it either. Guessing what get_llmobs_agent_loop does from its name would be invention, so this page leaves its role open.
get_llmobs_agent_loop, the general approvals rule is the only guidance that covers it.get_llmobs_evaluator
get_llmobs_evaluator appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_evaluator, and no Claude help page describes it either. Guessing what get_llmobs_evaluator does from its name would be invention, so this page leaves its role open.
get_llmobs_evaluator, the general approvals rule is the only guidance that covers it.list_llmobs_evals
list_llmobs_evals appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_llmobs_evals, and no Claude help page describes it either. Guessing what list_llmobs_evals does from its name would be invention, so this page leaves its role open.
list_llmobs_evals, the general approvals rule is the only guidance that covers it.get_llmobs_eval_aggregate_stats
get_llmobs_eval_aggregate_stats appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_eval_aggregate_stats, and no Claude help page describes it either. Guessing what get_llmobs_eval_aggregate_stats does from its name would be invention, so this page leaves its role open.
get_llmobs_eval_aggregate_stats, the general approvals rule is the only guidance that covers it.get_llmobs_experiment_summary
get_llmobs_experiment_summary appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_experiment_summary, and no Claude help page describes it either. Guessing what get_llmobs_experiment_summary does from its name would be invention, so this page leaves its role open.
get_llmobs_experiment_summary, the general approvals rule is the only guidance that covers it.list_llmobs_experiment_events
list_llmobs_experiment_events appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_llmobs_experiment_events, and no Claude help page describes it either. Guessing what list_llmobs_experiment_events does from its name would be invention, so this page leaves its role open.
list_llmobs_experiment_events, the general approvals rule is the only guidance that covers it.get_llmobs_experiment_event
get_llmobs_experiment_event appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_experiment_event, and no Claude help page describes it either. Guessing what get_llmobs_experiment_event does from its name would be invention, so this page leaves its role open.
get_llmobs_experiment_event, the general approvals rule is the only guidance that covers it.get_llmobs_experiment_metric_values
get_llmobs_experiment_metric_values appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_experiment_metric_values, and no Claude help page describes it either. Guessing what get_llmobs_experiment_metric_values does from its name would be invention, so this page leaves its role open.
get_llmobs_experiment_metric_values, the general approvals rule is the only guidance that covers it.get_llmobs_experiment_dimension_values
get_llmobs_experiment_dimension_values appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_llmobs_experiment_dimension_values, and no Claude help page describes it either. Guessing what get_llmobs_experiment_dimension_values does from its name would be invention, so this page leaves its role open.
get_llmobs_experiment_dimension_values, the general approvals rule is the only guidance that covers it.get_network_path_test_runs
get_network_path_test_runs appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_network_path_test_runs, and no Claude help page describes it either. Guessing what get_network_path_test_runs does from its name would be invention, so this page leaves its role open.
get_network_path_test_runs, the general approvals rule is the only guidance that covers it.aap_onboarding
aap_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name aap_onboarding, and no Claude help page describes it either. Guessing what aap_onboarding does from its name would be invention, so this page leaves its role open.
aap_onboarding, the general approvals rule is the only guidance that covers it.code_coverage_onboarding
code_coverage_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name code_coverage_onboarding, and no Claude help page describes it either. Guessing what code_coverage_onboarding does from its name would be invention, so this page leaves its role open.
code_coverage_onboarding, the general approvals rule is the only guidance that covers it.docker_onboarding
docker_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name docker_onboarding, and no Claude help page describes it either. Guessing what docker_onboarding does from its name would be invention, so this page leaves its role open.
docker_onboarding, the general approvals rule is the only guidance that covers it.ecs_onboarding
ecs_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name ecs_onboarding, and no Claude help page describes it either. Guessing what ecs_onboarding does from its name would be invention, so this page leaves its role open.
ecs_onboarding, the general approvals rule is the only guidance that covers it.studio_onboarding
studio_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name studio_onboarding, and no Claude help page describes it either. Guessing what studio_onboarding does from its name would be invention, so this page leaves its role open.
studio_onboarding, the general approvals rule is the only guidance that covers it.search_security_findings
search_security_findings appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_security_findings, and no Claude help page describes it either. Guessing what search_security_findings does from its name would be invention, so this page leaves its role open.
search_security_findings, the general approvals rule is the only guidance that covers it.analyze_security_findings
analyze_security_findings appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name analyze_security_findings, and no Claude help page describes it either. Guessing what analyze_security_findings does from its name would be invention, so this page leaves its role open.
analyze_security_findings, the general approvals rule is the only guidance that covers it.security_findings_schema
security_findings_schema appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name security_findings_schema, and no Claude help page describes it either. Guessing what security_findings_schema does from its name would be invention, so this page leaves its role open.
security_findings_schema, the general approvals rule is the only guidance that covers it.security_signals_schema
security_signals_schema appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name security_signals_schema, and no Claude help page describes it either. Guessing what security_signals_schema does from its name would be invention, so this page leaves its role open.
security_signals_schema, the general approvals rule is the only guidance that covers it.search_cws_agent_events
search_cws_agent_events appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_cws_agent_events, and no Claude help page describes it either. Guessing what search_cws_agent_events does from its name would be invention, so this page leaves its role open.
search_cws_agent_events, the general approvals rule is the only guidance that covers it.cws_agent_events_schema
cws_agent_events_schema appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name cws_agent_events_schema, and no Claude help page describes it either. Guessing what cws_agent_events_schema does from its name would be invention, so this page leaves its role open.
cws_agent_events_schema, the general approvals rule is the only guidance that covers it.list_datadog_skills
list_datadog_skills appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_datadog_skills, and no Claude help page describes it either. Guessing what list_datadog_skills does from its name would be invention, so this page leaves its role open.
list_datadog_skills, the general approvals rule is the only guidance that covers it.load_datadog_skill
load_datadog_skill appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name load_datadog_skill, and no Claude help page describes it either. Guessing what load_datadog_skill does from its name would be invention, so this page leaves its role open.
load_datadog_skill, the general approvals rule is the only guidance that covers it.search_pr_insights
search_pr_insights appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name search_pr_insights, and no Claude help page describes it either. Guessing what search_pr_insights does from its name would be invention, so this page leaves its role open.
search_pr_insights, the general approvals rule is the only guidance that covers it.get_prs_by_head_branch
get_prs_by_head_branch appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_prs_by_head_branch, and no Claude help page describes it either. Guessing what get_prs_by_head_branch does from its name would be invention, so this page leaves its role open.
get_prs_by_head_branch, the general approvals rule is the only guidance that covers it.update_datadog_workflow_with_agent_trigger
update_datadog_workflow_with_agent_trigger appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name update_datadog_workflow_with_agent_trigger, and no Claude help page describes it either. Guessing what update_datadog_workflow_with_agent_trigger does from its name would be invention, so this page leaves its role open.
update_datadog_workflow_with_agent_trigger, the general approvals rule is the only guidance that covers it.get_datadog_security_detection_rule
get_datadog_security_detection_rule appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_datadog_security_detection_rule, and no Claude help page describes it either. Guessing what get_datadog_security_detection_rule does from its name would be invention, so this page leaves its role open.
get_datadog_security_detection_rule, the general approvals rule is the only guidance that covers it.list_datadog_security_detection_rules
list_datadog_security_detection_rules appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_datadog_security_detection_rules, and no Claude help page describes it either. Guessing what list_datadog_security_detection_rules does from its name would be invention, so this page leaves its role open.
list_datadog_security_detection_rules, the general approvals rule is the only guidance that covers it.get_kafka_client_configuration
get_kafka_client_configuration appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_kafka_client_configuration, and no Claude help page describes it either. Guessing what get_kafka_client_configuration does from its name would be invention, so this page leaves its role open.
get_kafka_client_configuration, the general approvals rule is the only guidance that covers it.get_kafka_schema_registry_subject_versions
get_kafka_schema_registry_subject_versions appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name get_kafka_schema_registry_subject_versions, and no Claude help page describes it either. Guessing what get_kafka_schema_registry_subject_versions does from its name would be invention, so this page leaves its role open.
get_kafka_schema_registry_subject_versions, the general approvals rule is the only guidance that covers it.list_kafka_schema_registry_schemas
list_kafka_schema_registry_schemas appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_kafka_schema_registry_schemas, and no Claude help page describes it either. Guessing what list_kafka_schema_registry_schemas does from its name would be invention, so this page leaves its role open.
list_kafka_schema_registry_schemas, the general approvals rule is the only guidance that covers it.list_kafka_broker_configuration_versions
list_kafka_broker_configuration_versions appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_kafka_broker_configuration_versions, and no Claude help page describes it either. Guessing what list_kafka_broker_configuration_versions does from its name would be invention, so this page leaves its role open.
list_kafka_broker_configuration_versions, the general approvals rule is the only guidance that covers it.list_kafka_topic_configuration_versions
list_kafka_topic_configuration_versions appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_kafka_topic_configuration_versions, and no Claude help page describes it either. Guessing what list_kafka_topic_configuration_versions does from its name would be invention, so this page leaves its role open.
list_kafka_topic_configuration_versions, the general approvals rule is the only guidance that covers it.read_kafka_messages
read_kafka_messages appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name read_kafka_messages, and no Claude help page describes it either. Guessing what read_kafka_messages does from its name would be invention, so this page leaves its role open.
read_kafka_messages, the general approvals rule is the only guidance that covers it.retry_datadog_ci_job
retry_datadog_ci_job appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name retry_datadog_ci_job, and no Claude help page describes it either. Guessing what retry_datadog_ci_job does from its name would be invention, so this page leaves its role open.
retry_datadog_ci_job, the general approvals rule is the only guidance that covers it.generate_monitor_message
generate_monitor_message appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name generate_monitor_message, and no Claude help page describes it either. Guessing what generate_monitor_message does from its name would be invention, so this page leaves its role open.
generate_monitor_message, the general approvals rule is the only guidance that covers it.recommend_monitor_threshold
recommend_monitor_threshold appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name recommend_monitor_threshold, and no Claude help page describes it either. Guessing what recommend_monitor_threshold does from its name would be invention, so this page leaves its role open.
recommend_monitor_threshold, the general approvals rule is the only guidance that covers it.linux_onboarding
linux_onboarding appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name linux_onboarding, and no Claude help page describes it either. Guessing what linux_onboarding does from its name would be invention, so this page leaves its role open.
linux_onboarding, the general approvals rule is the only guidance that covers it.list_llmobs_evals_by_ml_app
list_llmobs_evals_by_ml_app appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name list_llmobs_evals_by_ml_app, and no Claude help page describes it either. Guessing what list_llmobs_evals_by_ml_app does from its name would be invention, so this page leaves its role open.
list_llmobs_evals_by_ml_app, the general approvals rule is the only guidance that covers it.upsert_llmobs_evaluator
upsert_llmobs_evaluator appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name upsert_llmobs_evaluator, and no Claude help page describes it either. Guessing what upsert_llmobs_evaluator does from its name would be invention, so this page leaves its role open.
upsert_llmobs_evaluator, the general approvals rule is the only guidance that covers it.delete_llmobs_evaluator
delete_llmobs_evaluator appears on the directory sheet by name only. Datadog's tools reference, read in full in September 2026, has no entry under the exact name delete_llmobs_evaluator, and no Claude help page describes it either. Guessing what delete_llmobs_evaluator does from its name would be invention, so this page leaves its role open.
delete_llmobs_evaluator, the general approvals rule is the only guidance that covers it.What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping reading open and closing writing. That setting applies to everyone and nobody gets around it from their own account. Finally, Claude works with your rights and nothing beyond: a log, trace or dashboard your Datadog role cannot see stays out of its reach too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog rather than a gap in our reading.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. For the live state of this one, go to Datadog's sheet in the official directory, the only place that shows it.
Where the Claude Datadog connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a metric crosses a threshold. That remains a monitor's job.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it, so the facts come from the directory sheet and Datadog's MCP Server pages. Datadog says its server is under significant development, which explains why many names on the sheet no longer match its reference. The partner badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. The Integrations hub gathers the automation families.
Need help connecting Datadog to Claude?
A person reads every message.
