Upload multiple documents in batch
AI agents use upload_documents to create or update resources in LightRAG MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LightRAG MCP Server environment.
This tool creates or ingests new documents into the LightRAG knowledge system. While uploads are reversible (documents can be deleted via delete_document), the batch operation and potential to ingest large volumes of data warrant a medium severity rating. The tool does not execute arbitrary code, delete irreversibly, or move money, making Write the appropriate category.
From the tool's definition Tool name 'upload_documents' with description 'Upload multiple documents in batch' indicates creation of new data in the system. The batch operation suggests multiple reversible modifications.
Attacks that exploit this kind of access
Upload multiple documents in batch. It is categorised as a Write tool in the LightRAG MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LightRAG MCP Server MCP server in PolicyLayer and add a rule for upload_documents: 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 LightRAG MCP Server. Nothing to install.
upload_documents 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 upload_documents 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 upload_documents. 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.
upload_documents is provided by the LightRAG MCP Server MCP server (lalitsuryan/lightragmcp). 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 →