Run MongoDB aggregation pipeline
AI agents invoke aggregate to trigger actions in Enhanced 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.
While aggregation pipelines are technically read operations in terms of not modifying data, they are classified as Execute rather than Read because: (1) they run arbitrary pipeline logic on the server, (2) the blast radius of a misconfigured pipeline could cause resource exhaustion or unintended data exposure depending on the stages provided, and (3) an AI agent with unconstrained access could construct pipelines…
From the tool's definition Tool explicitly runs a MongoDB aggregation pipeline, which is a server-side operation that processes and transforms data according to pipeline stages.
Attacks that exploit this kind of access
Run MongoDB aggregation pipeline. It is categorised as a Execute tool in the Enhanced MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Enhanced MCP Server MCP server in PolicyLayer and add a rule for 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 Enhanced MCP Server. Nothing to install.
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 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 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.
aggregate is provided by the Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →