AI agents invoke aggregate to trigger actions in 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.
Although the server is described as 'read-only' (suggesting no data modification), the aggregate tool itself executes non-trivial database operations whose effects depend on the pipeline argument. Aggregation pipelines can be computationally expensive, trigger side-effects via external stages (e.g., $out, $merge in extended MongoDB), or be chained to modify behavior of dependent systems.
From the tool's definition Tool description states 'Run a MongoDB aggregation pipeline' — aggregation pipelines execute arbitrary query logic and can perform complex transformations, filtering, grouping, and computed operations on data.
Documented attack patterns abuse exactly the kind of access aggregate gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MongoDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for aggregate:
{
"version": "1",
"default": "deny",
"tools": {
"aggregate": {
"limits": [
{
"counter": "aggregate_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}aggregate stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run a MongoDB aggregation pipeline. It is categorised as a Execute tool in the MongoDB MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MongoDB 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 MongoDB 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 MongoDB MCP Server MCP server (mongodb-developer/mongodb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MongoDB MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MongoDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.