Get all events for the project
AI agents call events_get_all to retrieve information from MongoDB Atlas 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 event data from a MongoDB Atlas project without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query operation with minimal blast radius if misused by an AI agent—worst case being exposure of project event logs which may contain sensitive operational information, but no actual harm to infrastructure or data.
From the tool's definition Tool name 'events_get_all' and description 'Get all events for the project' indicate a retrieval operation with no modification or destructive capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all events for the project. It is categorised as a Read tool in the MongoDB Atlas MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MongoDB Atlas MCP Server MCP server in PolicyLayer and add a rule for events_get_all: 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 Atlas MCP Server. Nothing to install.
events_get_all 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 events_get_all 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 events_get_all. 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.
events_get_all is provided by the MongoDB Atlas MCP Server MCP server (montumodi/mongodb-atlas-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 →