Update a sandbox inbox name or email username
AI agents use update-sandbox-inbox to create or update resources in Mcp Mailtrap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Mailtrap environment.
This tool modifies inbox metadata (name or email username) reversibly without deleting data or executing external code. It qualifies as Write rather than Read (retrieves data only) or Execute (runs code). Severity is medium because misconfiguration could disrupt email testing workflows, but the change is reversible and limited in scope to sandbox infrastructure.
From the tool's definition Tool explicitly performs "Update a sandbox inbox name or email username" — modifying existing inbox configuration data.
Attacks that exploit this kind of access
Update a sandbox inbox name or email username. It is categorised as a Write tool in the Mcp Mailtrap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for update-sandbox-inbox: 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.
update-sandbox-inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update-sandbox-inbox 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 update-sandbox-inbox. 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.
update-sandbox-inbox 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 →