List Service Level Objectives (SLOs) from Datadog. SLOs define service level targets and track performance against those targets.
AI agents call list_slos 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 and queries SLO definitions and their performance metrics from Datadog. It has no side effects, does not modify data, execute commands, delete resources, or move money. The action is informational only, making it a Read operation with low risk if misused by an agent (worst case: unnecessary API calls or information disclosure of monitoring metadata).
From the tool's definition Tool name 'list_slos' and description state it 'List[s] Service Level Objectives' and 'track[s] performance' — pure data retrieval with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access list_slos 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_slos:
{
"version": "1",
"default": "deny",
"tools": {
"list_slos": {}
}
} list_slos 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 Service Level Objectives (SLOs) from Datadog. SLOs define service level targets and track performance against those targets. 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_slos: 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_slos 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_slos 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_slos. 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_slos 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.