Get health metrics for a service including latency, error rate, and throughput.
AI agents call get_service_health to retrieve information from MCP Datadog Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns observability data about service health without modifying any state, executing code, or triggering external operations. It is a straightforward read operation on monitoring data, presenting minimal risk of misuse by an AI agent.
From the tool's definition Tool retrieves health metrics (latency, error rate, throughput) for a service. The description uses 'get' and 'health metrics' which indicates data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
Get health metrics for a service including latency, error rate, and throughput. It is categorised as a Read tool in the MCP Datadog Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Datadog Server MCP server in PolicyLayer and add a rule for get_service_health: 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 MCP Datadog Server. Nothing to install.
get_service_health 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 get_service_health 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 get_service_health. 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.
get_service_health is provided by the MCP Datadog Server MCP server (micaelmalta/mcp-server-datadog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →