remove_tag_from_contact · Systemeio MCP: Risk & Policy

WHAT IT DOES

What remove_tag_from_contact does on Systemeio

AI agents use remove_tag_from_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 remove_tag_from_contact needs a policy

Removing a tag from a contact modifies the contact's data by disassociating a tag, but this is generally a reversible operation (the tag can be re-added). It falls under Write rather than Destructive since the tag itself and the contact both still exist; only the association is removed. Misuse could affect segmentation and automation workflows, giving it medium severity.

From the tool's definition Remove a tag from a contact

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_tag_from_contact Rate-limited

remove_tag_from_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": {
    "remove_tag_from_contact": {
      "limits": [
        {
          "counter": "remove_tag_from_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 remove_tag_from_contact

What does the remove_tag_from_contact tool do? +

Remove a tag from a 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 remove_tag_from_contact? +

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

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

Can I rate-limit remove_tag_from_contact? +

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

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

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