Get list of all alerts with advanced filtering options. Returns a reduced set of fields for each alert. API-side filters: - resolved: Filter by resolution status - timeInterval: Time interval filter Advanced Filtering (MCP server-side): - Use valueType/value to filter the result set after mapping...
AI agents call list_alerts to retrieve information from NDB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries alert data from the Nutanix Database Service environment. The filtering options (resolved, timeInterval, valueType/value) are all read-only query parameters that narrow the result set without modifying any underlying data. No side effects, state changes, or external operations are triggered. This is a standard informational read operation with minimal risk.
From the tool's definition Tool description states 'Get list of all alerts' and 'Returns a reduced set of fields for each alert.' The only operations mentioned are filtering and retrieval with no modifications, creations, deletions, or code execution.
Attacks that exploit this kind of access
Get list of all alerts with advanced filtering options. Returns a reduced set of fields for each alert. API-side filters: - resolved: Filter by resolution status - timeInterval: Time interval filter Advanced Filtering (MCP server-side): - Use valueType/value to filter the result set after mapping. Supports all returned fields, including status, severity, type, entityType, entityId, entityName, dateCreated, resolved, acknowledged, etc. - Operators: !value (not), >value/<value (comparison), *value* (contains) - Multiple filters: combine with comma-separated valueType/value pairs - Examples: - Find unresolved critical alerts: valueType=. It is categorised as a Read tool in the NDB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NDB MCP Server MCP server in PolicyLayer and add a rule for 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 NDB MCP Server. Nothing to install.
list_alerts 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 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.
Set action: deny in the PolicyLayer policy for 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.
list_alerts is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). 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 →