import_contacts · XEM Email MCP Server MCP: Risk & Policy

WHAT IT DOES

What import_contacts does on XEM Email MCP Server

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

WHY IT NEEDS A POLICY

Why import_contacts needs a policy

This tool creates new contact records in the system (Write category), potentially in bulk. While not destructive since contacts can be removed, and not Execute since it doesn't run arbitrary code, the high confidence in Write classification reflects the significant blast radius: an attacker could poison contact lists with fraudulent emails, spam addresses, or malicious payloads that might be used in phishing…

From the tool's definition Tool description states 'Import contacts from a CSV file to a mailing list using file upload' — this creates or modifies contact data in the mailing list system. The ability to bulk import from CSV files means potentially large-scale data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_contacts Rate-limited

import_contacts 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": {
    "import_contacts": {
      "limits": [
        {
          "counter": "import_contacts_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 XEM Email MCP Server, so you can run agents against it safely.

FAQ

Questions about import_contacts

What does the import_contacts tool do? +

Import contacts from a CSV file to a mailing list using file upload. It is categorised as a Write tool in the XEM Email 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 import_contacts? +

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

What risk level is import_contacts? +

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

Can I rate-limit import_contacts? +

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

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

import_contacts is provided by the XEM Email MCP Server MCP server (mailxem/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.