This record as markdown: /tools/aiwerk-mcp-server-ghl/medias-update-media-object.md
What medias_update_media_object does on Ghl
AI agents use medias_update_media_object to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique identifier of the file or folder to update |
name | string | Yes | New name for the file or folder |
altId | string | — | Location identifier that owns the file or folder Defaults to GHL_LOCATION_ID when omitted. |
altType | string | — | Type of entity that owns the file or folder Defaults to GHL_LOCATION_ID when omitted. |
Parameters from the server's own tool schema.
Why medias_update_media_object is rated Medium
An AI agent can call medias_update_media_object faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs medias_update_media_object 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_update_media_object, this is the rule to start with:
medias_update_media_object stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ghl, apply this rule, and every medias_update_media_object call is checked against it from then on.
Questions about medias_update_media_object
Update File/ Folder. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
medias_update_media_object accepts 4 parameters: id, name, altId, altType. Required: id, name. 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_update_media_object: 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_update_media_object 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 medias_update_media_object 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_update_media_object. 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_update_media_object 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.
This server
Across the catalogue