Run a MongoDB aggregation pipeline with write stages disabled by default.
AI agents invoke aggregate-documents to trigger actions in Universal Mcp Toolkit. 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.
This tool executes arbitrary MongoDB aggregation queries, whose side effects depend on the pipeline stages provided as arguments. Although write stages are reportedly disabled, executing aggregation pipelines (which can perform complex transformations, reads, and filtered operations) constitutes code/query execution.
From the tool's definition Run a MongoDB aggregation pipeline with write stages disabled by default." The tool executes a database aggregation pipeline, which is an arbitrary operation that can query and transform data based on arguments.
Attacks that exploit this kind of access
Run a MongoDB aggregation pipeline with write stages disabled by default. It is categorised as a Execute tool in the Universal Mcp Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Universal Mcp Toolkit MCP server in PolicyLayer and add a rule for aggregate-documents: 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 Universal Mcp Toolkit. Nothing to install.
aggregate-documents 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-documents 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-documents. 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-documents is provided by the Universal Mcp Toolkit MCP server (markgatcha/universal-mcp-toolkit). 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 →