往知识库里加文件
AI agents use add_file to create or update resources in RAG MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAG MCP Server environment.
This tool creates or modifies data in the knowledge base by adding files. It is reversible (files can be deleted via delete_file), so it qualifies as Write rather than Destructive.
From the tool's definition Tool name 'add_file' and description '往知识库里加文件' (add file to knowledge base) — creates/uploads new data to a knowledge base without removing or executing anything.
Attacks that exploit this kind of access
往知识库里加文件. It is categorised as a Write tool in the RAG MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RAG MCP Server MCP server in PolicyLayer and add a rule for add_file: 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 RAG MCP Server. Nothing to install.
add_file 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_file 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_file. 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_file is provided by the RAG MCP Server MCP server (sglwsjxh/rag-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 →