create_contact · Zimbra MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_contact does on Zimbra MCP Server

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

WHY IT NEEDS A POLICY

Why create_contact needs a policy

Creating contacts is a reversible modification operation—new contacts can be deleted or modified afterward. This is clearly Write rather than Destructive. Severity is medium because contact creation could be abused to add malicious or spam contacts to someone's address book, but the impact is limited to contact pollution rather than data destruction or financial harm.

From the tool's definition Tool name 'create_contact' indicates creation of contact data. Server description states it 'Supports searching, sending, drafting emails, managing contacts, tags, and calendar events.' The verb 'create' establishes this as a Write operation that adds new…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_contact Rate-limited

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

FAQ

Questions about create_contact

What does the create_contact tool do? +

create_contact. It is categorised as a Write tool in the Zimbra 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 create_contact? +

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

What risk level is create_contact? +

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

Can I rate-limit create_contact? +

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

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

create_contact is provided by the Zimbra MCP Server MCP server (jeremie-lesage/zimbra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.