Get a sandbox project by ID, including its inboxes and email counts
AI agents call get-sandbox-project to retrieve information from Mcp Mailtrap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project metadata and statistics (inboxes, email counts) from a sandbox environment. It performs a read-only query operation with no capability to modify, delete, execute code, or trigger external actions. The sandbox context further limits risk. Severity is low due to minimal blast radius if misused—an AI agent could only retrieve existing project information.
From the tool's definition Tool name 'get-sandbox-project' and description 'Get a sandbox project by ID, including its inboxes and email counts' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get a sandbox project by ID, including its inboxes and email counts. It is categorised as a Read tool in the Mcp Mailtrap MCP Server, which means it retrieves data without modifying state.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for get-sandbox-project: 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 Mcp Mailtrap. Nothing to install.
get-sandbox-project 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 get-sandbox-project 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 get-sandbox-project. 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.
get-sandbox-project is provided by the Mcp Mailtrap MCP server (mcp-mailtrap). 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 →