Add a PDF or text file to the knowledge base.
AI agents use add_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.
The tool creates new entries in a knowledge base, which is a reversible write operation. Severity is medium because while documents can be added, they can presumably be removed or edited (suggested by the sibling tool context), and the blast radius is limited to corrupting or polluting a documentation index for a Commodore 64 knowledge system—not a critical production system.
From the tool's definition Tool is named 'add_document' and explicitly described as 'Add a PDF or text file to the knowledge base.' This is a create/insert operation that modifies the knowledge base by adding new documents.
Attacks that exploit this kind of access
Add a PDF or text file to the knowledge base. 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 add_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.
add_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 add_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 add_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.
add_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 →