datadog_get_events

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/datadog-get-events.md

WHAT IT DOES

What datadog_get_events does on Integrations MCP

AI agents call datadog_get_events 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.

RISK

Why datadog_get_events is rated Low

This tool retrieves event data from Datadog, a monitoring and observability platform. While the description is empty (lowering confidence slightly), the naming convention strongly suggests a read-only operation.

From the tool's definition Tool name 'datadog_get_events' indicates retrieval of events from Datadog monitoring platform. The 'get' prefix is consistent with read operations that query and retrieve data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs datadog_get_events 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_events, this is the rule to start with:

datadog_get_events Allowed

datadog_get_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datadog_get_events": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every datadog_get_events call is checked against it from then on.

FAQ

Questions about datadog_get_events

What does the datadog_get_events tool do? +

datadog_get_events 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.

How do I enforce a policy on datadog_get_events? +

Register the Integrations MCP server in PolicyLayer and add a rule for datadog_get_events: 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.

What risk level is datadog_get_events? +

datadog_get_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit datadog_get_events? +

Yes. Add a rate_limit block to the datadog_get_events 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.

How do I block datadog_get_events completely? +

Set action: deny in the PolicyLayer policy for datadog_get_events. 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.

What MCP server provides datadog_get_events? +

datadog_get_events 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.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →