Get metadata for a specific metric
AI agents call get_metric_metadata 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 queries and retrieves metric metadata from Datadog without any side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch)'. The 'get' prefix and retrieval-only nature indicate no risk of data modification or destructive operations. Severity is low because metadata retrieval poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_metric' and description states 'Get metadata for a specific metric' - purely a retrieval operation with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get metadata for a specific metric. 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 get_metric_metadata: 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.
get_metric_metadata 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_metric_metadata 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_metric_metadata. 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_metric_metadata is provided by the Datadog MCP Server MCP server (ppandrangi/datadog-mcp). 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 →