Get list of operations (short info) with all supported filters from the NDB API. Available parameters: - dbserverId: Filter by database server ID - eraServer: Filter by era server (boolean) - ip: Filter by IP address - clientId: Filter by client ID - status: Filter by operation status - type: Fil...
AI agents call list_operations 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 retrieves and queries operation records from the NDB API using various filter criteria. It performs no data modification, deletion, or external execution. The boolean flags (hideSubops, eraServer, systemTriggered, etc.) are display/filter options, not mutation controls.
From the tool's definition Tool name 'list_operations' and description 'Get list of operations (short info)' indicate data retrieval. All parameters are filters (dbserverId, status, type, ip, etc.) used for querying without modifying state. No side effects are mentioned or implied.
Attacks that exploit this kind of access
Get list of operations (short info) with all supported filters from the NDB API. Available parameters: - dbserverId: Filter by database server ID - eraServer: Filter by era server (boolean) - ip: Filter by IP address - clientId: Filter by client ID - status: Filter by operation status - type: Filter by operation type - hideSubops: Hide sub-operations (boolean) - systemTriggered: Filter by system-triggered operations (boolean) - userTriggered: Filter by user-triggered operations (boolean) - scheduled: Filter by scheduled operations (boolean) - dateSubmitted: Filter by submission date (string) - fromTime: Filter by start time (string) - toTime: Filter by end time (string) - days: Number of days to look back (string) - entityId: Filter by entity ID - entityName: Filter by entity name - entityType: Filter by entity type - timeZone: Time zone for timestamps (default: UTC) - descending: Sort descending (boolean) - operationId: Filter by operation ID - timestamp: Filter by timestamp (string) - limit: Limit number of results (string) Example usage: - List all failed operations in the last 7 days: status=. 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_operations: 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_operations 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_operations 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_operations. 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_operations 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 →