Delete_Permission
A destructive tool on the Files Com MCP server.
This record as markdown: /tools/com-files-python-mcp/delete-permission.md
What Delete_Permission does on Files Com
AI agents call Delete_Permission to permanently remove resources in Files Com, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why Delete_Permission is rated Critical
Deleting a permission irreversibly removes access rights and cannot be undone without manual intervention to recreate the permission. This is a destructive operation that permanently alters system state. While not a financial transaction, the high severity reflects that unauthorized deletion of permissions could lock out legitimate users or expose resources.
From the tool's definition Tool name is 'Delete_Permission' and description states 'Delete Permission'. The verb 'Delete' combined with the action of removing permissions indicates irreversible modification of access control state.
Attacks that exploit this kind of access
The rule that runs Delete_Permission safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Files Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For Delete_Permission, this is the rule to start with:
Delete_Permission is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Files Com, apply this rule, and every Delete_Permission call is checked against it from then on.
Questions about Delete_Permission
Delete_Permission is a destructive tool on the Files Com MCP server. It is categorised as a Destructive tool in the Files Com MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Files Com MCP server in PolicyLayer and add a rule for Delete_Permission: 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 Files Com. Nothing to install.
Delete_Permission 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 Delete_Permission 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 Delete_Permission. 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.
Delete_Permission is provided by the Files Com MCP server (files-com-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Files Com, and thousands of servers like it.
Across the catalogue