List all service definitions from Datadog. Service definitions describe the structure, ownership, and metadata of services in your organization.
AI agents call list_service_definitions to retrieve information from Datadog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves organizational metadata about services without performing any side effects, creation, modification, deletion, or external operations. It is a pure read operation that queries service definition data from Datadog, consistent with tools like 'get_logs' and 'get_teams' on the same server.
From the tool's definition Tool name 'list_service_definitions' and description 'List all service definitions' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access list_service_definitions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Datadog MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_service_definitions:
{
"version": "1",
"default": "deny",
"tools": {
"list_service_definitions": {}
}
} list_service_definitions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all service definitions from Datadog. Service definitions describe the structure, ownership, and metadata of services in your organization. It is categorised as a Read tool in the Datadog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Datadog MCP Server MCP server in PolicyLayer and add a rule for list_service_definitions: 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 Datadog MCP Server. Nothing to install.
list_service_definitions 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 list_service_definitions 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 list_service_definitions. 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.
list_service_definitions is provided by the Datadog MCP Server MCP server (shelfio/datadog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Datadog MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Datadog MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.