MCP server

io.github.us-all/datadog

mcp:us-all/datadog-mcp-server

Datadog MCP — 165 tools for metrics, monitors, logs, APM, RUM, incidents, CI/CD, fleet

awesome-mcp-servers Glama MCP Registry

Verdict

Inconclusive

The analysis could not cover enough of the artifact to decide.

Analyzed Oct 26, 2026, 12:33 UTC at e943fa7

findings

—

highest severity

threat classes

files scanned

1,054/1,054

checks satisfied

package advisories

Why this verdict

inconclusive: gap dynamic_metadata at src/index.ts

Security findings 0

No individual findings recorded

The inconclusive verdict rests on the coverage gaps below; 1 candidate finding was refuted on review.

Refuted findings 1

Candidates the review stage examined and rejected, kept for transparency.

Persistence

highRefutedlow confidence

The createFleetDeploymentConfigure tool lets the agent push arbitrary merge-patch or delete operations on named config files across Datadog Agent hosts matched by a query, which is a broad host-config write capability with no path restriction beyond the assertWriteAllowed gate.

src/tools/fleet.ts:151

operation.filePath = op.filePath;

Why it was refuted

The tool is the declared core capability of a Datadog MCP server (Fleet Automation configure), a thin wrapper over the Datadog API that is gated by assertWriteAllowed. Nothing is concealed, there is no agent-directed instruction, and the host-config write is performed by the Datadog API under the user's own credentials, not by hidden persistence.

Coverage gaps 1

Parts of the artifact the static analysis could not fully examine.

dynamic_metadata line 169: tool None input schema is computed: schema

src/index.ts