This record as markdown: /tools/aiwerk-mcp-server-ghl/medias-bulk-delete-media-objects.md
What medias_bulk_delete_media_objects does on Ghl
AI agents call medias_bulk_delete_media_objects 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 |
|---|---|---|---|
altId | string | — | Location identifier Defaults to GHL_LOCATION_ID when omitted. |
status | string | Yes | Status to set for the files (deleted or trashed) |
altType | string | — | Type of entity that owns the files Defaults to GHL_LOCATION_ID when omitted. |
filesToBeDeleted | array | Yes | Array of file objects to be deleted or trashed |
Parameters from the server's own tool schema.
Why medias_bulk_delete_media_objects is rated Critical
An AI agent that decides to call medias_bulk_delete_media_objects doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ghl is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs medias_bulk_delete_media_objects 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 medias_bulk_delete_media_objects, this is the rule to start with:
medias_bulk_delete_media_objects 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 medias_bulk_delete_media_objects call is checked against it from then on.
Questions about medias_bulk_delete_media_objects
Bulk Delete / Trash Files or Folders. 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.
medias_bulk_delete_media_objects accepts 4 parameters: altId, status, altType, filesToBeDeleted. Required: status, filesToBeDeleted. 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 medias_bulk_delete_media_objects: 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.
medias_bulk_delete_media_objects 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 medias_bulk_delete_media_objects 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 medias_bulk_delete_media_objects. 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.
medias_bulk_delete_media_objects is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). 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