update_contact · Systemeio MCP: Risk & Policy

WHAT IT DOES

What update_contact does on Systemeio

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

WHY IT NEEDS A POLICY

Why update_contact needs a policy

This tool creates or modifies data reversibly (the definition of Write category). While it changes contact information, the operation is not destructive (data can be updated again) and has moderate blast radius if misused by an agent—it could alter customer records, email addresses, or other contact fields, affecting business operations and customer communication, but changes are reversible.

From the tool's definition Tool name 'update_contact' and description 'Update an existing contact' indicate modification of existing data. The parent server manages 'contacts, tags, courses, and subscriptions' in a Systeme.io account, confirming this modifies customer/user records.

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 Systemeio, so you can run agents against it safely.

FAQ

Questions about update_contact

What does the update_contact tool do? +

Update an existing contact. It is categorised as a Write tool in the Systemeio 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 Systemeio 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 Systemeio. 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 Systemeio MCP server (snzeeee/mcp-server-systemeio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.