create_tag · Collectives MCP: Risk & Policy

WHAT IT DOES

What create_tag does on Collectives

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

WHY IT NEEDS A POLICY

Why create_tag needs a policy

Creating a tag is a write operation that modifies the state of the collective by adding metadata. It is reversible (the tag can be deleted via delete_tag, which is listed as a sibling tool), so it does not qualify as Destructive. It has minimal blast radius—tags are non-critical metadata with no side effects on data integrity or external systems.

From the tool's definition Tool name 'create_tag' and description explicitly states it creates a new tag in a Collective with a name and hex color code. This is a reversible creation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_tag Rate-limited

create_tag 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_tag": {
      "limits": [
        {
          "counter": "create_tag_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 Collectives, so you can run agents against it safely.

FAQ

Questions about create_tag

What does the create_tag tool do? +

Create a new tag in a Collective. Requires a name and a hex color code (e.g. It is categorised as a Write tool in the Collectives 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_tag? +

Register the Collectives MCP server in PolicyLayer and add a rule for create_tag: 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 Collectives. Nothing to install.

What risk level is create_tag? +

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

Can I rate-limit create_tag? +

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

Set action: deny in the PolicyLayer policy for create_tag. 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_tag? +

create_tag is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.