datadog_list_hosts
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/datadog-list-hosts.md
What datadog_list_hosts does on Integrations MCP
AI agents call datadog_list_hosts to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why datadog_list_hosts is rated Low
The tool appears to query Datadog infrastructure to enumerate hosts. While the description is empty (lowering confidence slightly), the naming convention 'list_*' is a strong indicator of a retrieval operation with no side effects. Listing hosts in a monitoring platform is a read-only query that does not modify, delete, or execute anything. It poses minimal risk to data integrity or system state.
From the tool's definition Tool name 'datadog_list_hosts' indicates a list operation, which retrieves or queries data. The 'list' verb is characteristic of Read operations that fetch information without modifying state.
Attacks that exploit this kind of access
The rule that runs datadog_list_hosts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datadog_list_hosts, this is the rule to start with:
datadog_list_hosts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every datadog_list_hosts call is checked against it from then on.
Questions about datadog_list_hosts
datadog_list_hosts is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for datadog_list_hosts: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Integrations MCP. Nothing to install.
datadog_list_hosts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the datadog_list_hosts rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for datadog_list_hosts. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
datadog_list_hosts is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue