Automatically generate tags for a document using AI analysis. Analyzes document content and suggests relevant tags across categories: hardware (sid, vic-ii), programming (assembly, basic), document type (tutorial, reference), and difficulty level (beginner, advanced). Requires LLM configuration (...
AI agents use auto_tag_document 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 creates or modifies document metadata (tags) based on AI analysis. While it does not delete data or execute arbitrary code, it reversibly writes classification information to documents. The severity is medium because incorrect automated tagging could degrade knowledge base usability and search quality, but the change is reversible through manual correction or removal of tags.
From the tool's definition Tool description states it 'Automatically generate tags for a document' and 'suggests relevant tags,' which modifies document metadata. The verb 'generate' combined with the action of adding tags to documents indicates data modification.
Attacks that exploit this kind of access
Automatically generate tags for a document using AI analysis. Analyzes document content and suggests relevant tags across categories: hardware (sid, vic-ii), programming (assembly, basic), document type (tutorial, reference), and difficulty level (beginner, advanced). Requires LLM configuration (set LLM_PROVIDER and API key). 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_document: 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_document 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_document 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_document. 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_document 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 →