remove_tags · Kontexta MCP: Risk & Policy

WHAT IT DOES

What remove_tags does on Kontexta

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

WHY IT NEEDS A POLICY

Why remove_tags needs a policy

The tool removes tag associations from a file but explicitly does not delete the file itself or the global tag definitions. This is a reversible metadata modification (tags can be re-attached), making it a Write operation rather than Destructive. The blast radius is low since only a tag-to-file link is removed, with no data loss.

From the tool's definition Detach one or more tag IDs from ONE file. Destructive on the link only — does NOT delete the file or the global tag definition

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_tags Rate-limited

remove_tags 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_tags": {
      "limits": [
        {
          "counter": "remove_tags_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 Kontexta, so you can run agents against it safely.

FAQ

Questions about remove_tags

What does the remove_tags tool do? +

Detach one or more tag IDs from ONE file. Destructive on the link only — does NOT delete the file or the global tag definition (orphan tags survive in. It is categorised as a Write tool in the Kontexta 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_tags? +

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

What risk level is remove_tags? +

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

Can I rate-limit remove_tags? +

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

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

remove_tags is provided by the Kontexta MCP server (safiyu/kontexta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.