This record as markdown: /tools/aiwerk-mcp-server-ghl/medias-fetch-media-content.md
What medias_fetch_media_content does on Ghl
AI agents call medias_fetch_media_content to retrieve information from Ghl without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Type |
altId | string | — | location Id Defaults to GHL_LOCATION_ID when omitted. |
limit | string | — | Number of files to show in the listing |
query | string | — | Query text |
offset | string | — | Number of files to skip in listing |
sortBy | string | Yes | Field to sorting the file listing by |
altType | string | — | AltType Defaults to GHL_LOCATION_ID when omitted. |
fetchAll | string | — | Fetch all files or folders |
parentId | string | — | parent id or folder id |
sortOrder | string | Yes | Direction in which file needs to be sorted |
Parameters from the server's own tool schema.
Why medias_fetch_media_content is rated Low
Even though medias_fetch_media_content only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs medias_fetch_media_content 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_fetch_media_content, this is the rule to start with:
medias_fetch_media_content is read-only, so it stays allowed. 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_fetch_media_content call is checked against it from then on.
Questions about medias_fetch_media_content
Get List of Files/ Folders. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
medias_fetch_media_content accepts 10 parameters: type, altId, limit, query, offset, sortBy, altType, fetchAll, parentId, sortOrder. Required: type, sortBy, sortOrder. 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_fetch_media_content: 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_fetch_media_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the medias_fetch_media_content 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_fetch_media_content. 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_fetch_media_content 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