drive_device_create · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What drive_device_create does on TrekMail MCP Server

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

WHY IT NEEDS A POLICY

Why drive_device_create needs a policy

Creating a device password is a write operation that modifies authentication infrastructure by introducing a new credential into the system. While not destructive (the password can be revoked), it has high severity because improperly created device passwords could grant unintended access to synchronized data. The tool creates a new, persistent authentication mechanism rather than merely querying or reading data.

From the tool's definition Tool name 'drive_device_create' and description 'Mint a new Drive sync-device password' indicates creation of authentication credentials for device synchronization.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

drive_device_create Rate-limited

drive_device_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": {
    "drive_device_create": {
      "limits": [
        {
          "counter": "drive_device_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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about drive_device_create

What does the drive_device_create tool do? +

Mint a new Drive sync-device password (a. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on drive_device_create? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_device_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 TrekMail MCP Server. Nothing to install.

What risk level is drive_device_create? +

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

Can I rate-limit drive_device_create? +

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

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

drive_device_create is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.