This record as markdown: /tools/ghl/delete-media-file.md
What delete_media_file does on Ghl
AI agents call delete_media_file to permanently remove resources in Ghl, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | ID of the file or folder to delete |
altId | string | — | Location or Agency ID (uses default location if not provided) |
altType | string | — | Context type (location or agency) |
Parameters from the server's own tool schema.
Why delete_media_file is rated Critical
The tool permanently removes files or folders from the media library with no undo capability. This is a destructive operation that cannot be reversed. The high severity reflects the potential for an AI agent to accidentally or maliciously delete important media assets belonging to a customer, causing data loss. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific file or folder from the media library' — this is irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_media_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_media_file, this is the rule to start with:
delete_media_file 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 Ghl, apply this rule, and every delete_media_file call is checked against it from then on.
Questions about delete_media_file
Delete a specific file or folder from the media library. It is categorised as a Destructive tool in the Ghl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_media_file accepts 3 parameters: id, altId, altType. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Ghl MCP server in PolicyLayer and add a rule for delete_media_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 Ghl. Nothing to install.
delete_media_file 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_media_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 delete_media_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.
delete_media_file is provided by the Ghl MCP server (ghl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ghl, and thousands of servers like it.
Across the catalogue