Get all canonical tags (semantic tag clusters).
AI agents call get_canonical_tags to retrieve information from Vector Task MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists semantic tag clusters. It performs a read-only query against the task management system's tag database with no side effects, no code execution, and no data modification. The operation is a straightforward data retrieval, fitting the 'Read' category.
From the tool's definition Tool name 'get_canonical_tags' and description 'Get all canonical tags' indicate a retrieval operation that queries existing canonical tag clusters without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get all canonical tags (semantic tag clusters). It is categorised as a Read tool in the Vector Task MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vector Task MCP Server MCP server in PolicyLayer and add a rule for get_canonical_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 Vector Task MCP Server. Nothing to install.
get_canonical_tags is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_canonical_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.
Set action: deny in the PolicyLayer policy for get_canonical_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.
get_canonical_tags 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →