Get all projects
AI agents call project_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 a list of projects from MongoDB Atlas without any side effects. It is a simple query operation that only reads data. The blast radius is minimal since it only exposes project metadata that would typically be available to an authenticated user with appropriate permissions. No data is modified, deleted, or executed, making this a straightforward Read category classification.
From the tool's definition Tool name is 'project_get_all' and description states 'Get all projects' — this is a retrieval operation with no modification or execution capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all projects. 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 project_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.
project_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 project_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 project_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.
project_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 →