mailosaur_devices_create · Mailosaur MCP: Risk & Policy

WHAT IT DOES

What mailosaur_devices_create does on Mailosaur MCP

AI agents use mailosaur_devices_create to create or update resources in Mailosaur MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailosaur MCP environment.

WHY IT NEEDS A POLICY

Why mailosaur_devices_create needs a policy

This tool creates a new virtual security device in the Mailosaur testing service. While creation is reversible (devices can be deleted via mailosaur_devices_delete), it results in a persistent change to the system state. The tool does not delete, execute arbitrary code, or move money, making it a Write operation.

From the tool's definition Tool name 'mailosaur_devices_create' and description 'Create a Mailosaur virtual security device from a base32 shared secret' explicitly indicates creation of a new resource (device) based on cryptographic input.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mailosaur_devices_create Rate-limited

mailosaur_devices_create 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": {
    "mailosaur_devices_create": {
      "limits": [
        {
          "counter": "mailosaur_devices_create_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 Mailosaur MCP, so you can run agents against it safely.

FAQ

Questions about mailosaur_devices_create

What does the mailosaur_devices_create tool do? +

Create a Mailosaur virtual security device from a base32 shared secret. It is categorised as a Write tool in the Mailosaur MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mailosaur_devices_create? +

Register the Mailosaur MCP server in PolicyLayer and add a rule for mailosaur_devices_create: 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 Mailosaur MCP. Nothing to install.

What risk level is mailosaur_devices_create? +

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

Can I rate-limit mailosaur_devices_create? +

Yes. Add a rate_limit block to the mailosaur_devices_create 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 mailosaur_devices_create completely? +

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

mailosaur_devices_create is provided by the Mailosaur MCP server (mrnewdelhi/mailosaur-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.