Execute MongoDB aggregation pipeline
AI agents invoke mongodb-aggregate to trigger actions in NestJS MongoDB MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Aggregation pipelines go beyond simple data retrieval; they execute arbitrary processing logic that can have significant side effects depending on the pipeline stages used. Stages like $out and $merge write data to collections, $function can execute custom JavaScript, and complex transformations can consume substantial resources.
From the tool's definition Tool is described as 'Execute MongoDB aggregation pipeline'. Aggregation pipelines in MongoDB can perform complex transformations, computations, and data processing operations.
Attacks that exploit this kind of access
Execute MongoDB aggregation pipeline. It is categorised as a Execute tool in the NestJS MongoDB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the NestJS MongoDB MCP Server MCP server in PolicyLayer and add a rule for mongodb-aggregate: 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 NestJS MongoDB MCP Server. Nothing to install.
mongodb-aggregate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the mongodb-aggregate 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 mongodb-aggregate. 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.
mongodb-aggregate is provided by the NestJS MongoDB MCP Server MCP server (jovicon/nestjs-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 →