update-sandbox-project · Mcp Mailtrap MCP: Risk & Policy

WHAT IT DOES

What update-sandbox-project does on Mcp Mailtrap

AI agents use update-sandbox-project 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.

WHY IT NEEDS A POLICY

Why update-sandbox-project needs a policy

Renaming a sandbox project is a Write operation: it creates or modifies data reversibly without destructive or executable side effects. Severity is medium because misuse could cause confusion or operational disruption in a sandbox environment (e.g., renaming a project to an obscure name), but the blast radius is limited to metadata changes in an isolated sandbox, not production systems or irreversible data loss.

From the tool's definition Tool description explicitly states 'Rename an existing sandbox project' — a reversible modification operation. The tool modifies project metadata rather than deleting or executing arbitrary code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-sandbox-project Rate-limited

update-sandbox-project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update-sandbox-project": {
      "limits": [
        {
          "counter": "update-sandbox-project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Mailtrap, so you can run agents against it safely.

FAQ

Questions about update-sandbox-project

What does the update-sandbox-project tool do? +

Rename an existing sandbox project. 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.

How do I enforce a policy on update-sandbox-project? +

Register the Mcp Mailtrap MCP server in PolicyLayer and add a rule for update-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.

What risk level is update-sandbox-project? +

update-sandbox-project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update-sandbox-project? +

Yes. Add a rate_limit block to the update-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.

How do I block update-sandbox-project completely? +

Set action: deny in the PolicyLayer policy for update-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.

What MCP server provides update-sandbox-project? +

update-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.