datadog_get_monitor
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/datadog-get-monitor.md
What datadog_get_monitor does on Integrations MCP
AI agents call datadog_get_monitor to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why datadog_get_monitor is rated Low
This tool retrieves monitor configuration or status from Datadog, a monitoring platform. It performs a data retrieval operation with no side effects. Even though the description is empty, the 'get_' prefix strongly indicates a read-only query. The blast radius of misuse is low—an agent could retrieve monitoring data but cannot modify systems or trigger actions.
From the tool's definition Tool name is 'datadog_get_monitor', where 'get' indicates retrieval of data without modification. No description provided, but the naming pattern is consistent with read operations (similar to airtable_get_record and amplitude_get_* tools in the sibling list).
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 Integrations MCP, 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 Integrations MCP, apply this rule, and every datadog_get_monitor call is checked against it from then on.
Questions about datadog_get_monitor
datadog_get_monitor is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations 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 Integrations MCP. 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 Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue