对FILE_PATH目录下的文件进行删除、重命名、读取和写入操作，以及图片压缩
AI agents call fileOperation to permanently remove resources in LuckyCola MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool explicitly supports delete operations on files, which are irreversible. It also supports rename, read, and write, but per the rules the most severe applicable category wins. File deletion is Destructive. The blast radius is high because an AI agent could delete arbitrary files under FILE_PATH, potentially causing irreversible data loss.
From the tool's definition 对FILE_PATH目录下的文件进行删除、重命名、读取和写入操作 — explicitly includes deletion ('删除') of files
Attacks that exploit this kind of access
对FILE_PATH目录下的文件进行删除、重命名、读取和写入操作，以及图片压缩. It is categorised as a Destructive tool in the LuckyCola MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuckyCola MCP Server MCP server in PolicyLayer and add a rule for fileOperation: 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 LuckyCola MCP Server. Nothing to install.
fileOperation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the fileOperation 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 fileOperation. 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.
fileOperation is provided by the LuckyCola MCP Server MCP server (mingle98/luckycola-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 →