canonical_tag_add · Vector Task MCP Server MCP

WHAT IT DOES

What canonical_tag_add does on Vector Task MCP Server

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

WHY IT NEEDS A POLICY

Why canonical_tag_add needs a policy

This tool creates or modifies tag data in the vector task management system. While the description is empty, the naming convention and context among sibling operations (list, remove, apply) strongly indicate it adds tags to a database. This is reversible (tags can be removed), so it falls under Write rather than Destructive.

From the tool's definition Tool name 'canonical_tag_add' indicates creation or modification of canonical tags within the task management system. The presence of sibling tools 'canonical_tag_remove' and 'canonical_tag_list' confirms this is part of a tag management subsystem.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

canonical_tag_add Rate-limited

canonical_tag_add 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": {
    "canonical_tag_add": {
      "limits": [
        {
          "counter": "canonical_tag_add_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 Vector Task MCP Server, so you can run agents against it safely.

FAQ

Questions about canonical_tag_add

What does the canonical_tag_add tool do? +

canonical_tag_add. It is categorised as a Write tool in the Vector Task MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on canonical_tag_add? +

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

What risk level is canonical_tag_add? +

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

Can I rate-limit canonical_tag_add? +

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

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

canonical_tag_add is provided by the Vector Task MCP Server MCP server (xsaven/vector-task-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.