Bulk auto-tag multiple documents using AI. Analyzes content and suggests relevant tags for all documents (or subset). Useful for initial organization or re-tagging collections. Can skip already-tagged documents and limit processing count. Requires LLM configuration.
AI agents use auto_tag_all to create or update resources in TDZ C64 Knowledge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TDZ C64 Knowledge environment.
This tool writes AI-generated tags to multiple documents in bulk. It modifies document metadata (tags) across a potentially large collection, which is a Write operation. While reversible in principle (tags could be removed), the bulk nature raises the severity to medium since misuse could mislabel an entire document collection. It does not delete data or execute arbitrary code.
From the tool's definition Bulk auto-tag multiple documents...suggests relevant tags for all documents...Can skip already-tagged documents
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Bulk auto-tag multiple documents using AI. Analyzes content and suggests relevant tags for all documents (or subset). Useful for initial organization or re-tagging collections. Can skip already-tagged documents and limit processing count. Requires LLM configuration. It is categorised as a Write tool in the TDZ C64 Knowledge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for auto_tag_all: 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 TDZ C64 Knowledge. Nothing to install.
auto_tag_all is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the auto_tag_all 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 auto_tag_all. 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.
auto_tag_all is provided by the TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). 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 →