datadog_get_monitor
Get details for a specific Datadog monitor.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/datadog-get-monitor.md
What datadog_get_monitor does on UnClick
AI agents call datadog_get_monitor to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key | string | Yes | Datadog API key |
app_key | string | Yes | Datadog Application key |
monitor_id | string | Yes | Monitor ID |
Parameters from the server's own tool schema.
Why datadog_get_monitor is rated Low
This tool retrieves monitor configuration and status information from Datadog. The verb 'Get' and lack of any language indicating creation, modification, deletion, or execution means this is a pure read operation. The blast radius of misuse is low—an agent could at most retrieve monitoring details, which typically contain less sensitive information than actual underlying metrics or infrastructure.
From the tool's definition Tool name 'datadog_get_monitor' and description 'Get details for a specific Datadog monitor' indicate a retrieval operation with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs datadog_get_monitor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datadog_get_monitor, this is the rule to start with:
datadog_get_monitor 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 UnClick, apply this rule, and every datadog_get_monitor call is checked against it from then on.
Questions about datadog_get_monitor
Get details for a specific Datadog monitor. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datadog_get_monitor accepts 3 parameters: api_key, app_key, monitor_id. Required: api_key, app_key, monitor_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for datadog_get_monitor: 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 UnClick. Nothing to install.
datadog_get_monitor 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_get_monitor 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_get_monitor. 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_get_monitor is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue