create_contact · Systemeio MCP: Risk & Policy

WHAT IT DOES

What create_contact does on Systemeio

AI agents use create_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 create_contact needs a policy

This tool creates new records (contacts) in Systeme.io and can trigger downstream automations. It is Write rather than Execute because contact creation is the primary action; automation triggering is a declared side effect of the write operation. However, the ability to trigger automations elevates severity from low to medium, as an AI agent could inadvertently enroll contacts in unintended campaigns or courses.

From the tool's definition The tool description states it 'Create[s] a new contact' and 'can trigger automations', indicating irreversible creation of data records and side effects that cascade through the system.

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

FAQ

Questions about create_contact

What does the create_contact tool do? +

Create a new contact in Systeme.io with an email address, optional locale, and custom fields. This can trigger automations (e.g., enrolling in a course or campaign). 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 create_contact? +

Register the Systemeio 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 Systemeio. 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 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.