update_contact · Zimbra MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_contact does on Zimbra MCP Server

AI agents use update_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 update_contact needs a policy

Updating a contact record creates or modifies data without permanently removing it, fitting the Write category. Severity is medium because contact data modification could affect communication routing, but is reversible. Confidence is 0.85 rather than higher because the tool description is empty, requiring inference from context (tool name and server capabilities).

From the tool's definition Tool name 'update_contact' combined with sibling tools 'create_contact' and 'delete_contact' indicates CRUD operations on contact data. Server description states it 'Supports...managing contacts.' Update operations modify data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_contact Rate-limited

update_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": {
    "update_contact": {
      "limits": [
        {
          "counter": "update_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 update_contact

What does the update_contact tool do? +

update_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 update_contact? +

Register the Zimbra MCP Server MCP server in PolicyLayer and add a rule for update_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 update_contact? +

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

Can I rate-limit update_contact? +

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

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

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