cdp_list_alerts

List triggered alerts (alert instances that have fired)

SERVERCDP MCP Server SOURCEatharva-joshi77/cdp-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/atharva-joshi77-cdp-mcp/cdp-list-alerts.md

WHAT IT DOES

What cdp_list_alerts does on CDP MCP Server

AI agents call cdp_list_alerts to retrieve information from CDP MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why cdp_list_alerts is rated Low

This tool retrieves or queries alert data without side effects. It does not create, modify, delete, or execute any operations—it simply returns information about alerts that have already been triggered. This is a standard Read operation with minimal risk if misused by an AI agent, as the worst case would be repeated queries of existing data.

From the tool's definition Tool name 'cdp_list_alerts' combined with description 'List triggered alerts (alert instances that have fired)' indicates a retrieval operation. The verb 'list' and 'fired' (past state) show this queries existing alert data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cdp_list_alerts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CDP MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cdp_list_alerts, this is the rule to start with:

cdp_list_alerts Allowed

cdp_list_alerts 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": {
    "cdp_list_alerts": {}
  }
}

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

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

FAQ

Questions about cdp_list_alerts

What does the cdp_list_alerts tool do? +

List triggered alerts (alert instances that have fired). It is categorised as a Read tool in the CDP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cdp_list_alerts? +

Register the CDP MCP Server MCP server in PolicyLayer and add a rule for cdp_list_alerts: 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 CDP MCP Server. Nothing to install.

What risk level is cdp_list_alerts? +

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

Can I rate-limit cdp_list_alerts? +

Yes. Add a rate_limit block to the cdp_list_alerts 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 cdp_list_alerts completely? +

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

cdp_list_alerts is provided by the CDP MCP Server MCP server (atharva-joshi77/cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CDP MCP Server, and thousands of servers like it.

This server

All 288 CDP MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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