add_tag_to_contact · Systemeio MCP: Risk & Policy

WHAT IT DOES

What add_tag_to_contact does on Systemeio

AI agents use add_tag_to_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 add_tag_to_contact needs a policy

This tool creates or modifies a relationship (tag assignment) on an existing contact record. While it may indirectly trigger automations, the primary action is Write—assigning metadata to an entity. It is reversible (unlike Destructive) and does not execute arbitrary code (unlike Execute).

From the tool's definition Tool description states "Assign a tag to a contact" which is a modification operation. The note that it "can trigger automations" indicates side effects but the tool itself performs a reversible write (tags can be removed via delete_tag).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_tag_to_contact Rate-limited

add_tag_to_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": {
    "add_tag_to_contact": {
      "limits": [
        {
          "counter": "add_tag_to_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 add_tag_to_contact

What does the add_tag_to_contact tool do? +

Assign a tag to a contact. This can trigger automations in Systeme.io (e.g., adding to a campaign, enrolling in a course). 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 add_tag_to_contact? +

Register the Systemeio MCP server in PolicyLayer and add a rule for add_tag_to_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 add_tag_to_contact? +

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

Can I rate-limit add_tag_to_contact? +

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

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

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