get_media_files
Get list of files and folders from the media library with filtering and search capabilities
This record as markdown: /tools/ghl/get-media-files.md
What get_media_files does on Ghl
AI agents call get_media_files 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 | — | Filter by type (file or folder) |
altId | string | — | Location or Agency ID (uses default location if not provided) |
limit | number | — | Number of files to show in the listing (max 100) |
query | string | — | Search query text to filter files by name |
offset | number | — | Number of files to skip in listing |
sortBy | string | — | Field to sort the file listing by (e.g., createdAt, name, size) |
altType | string | — | Context type (location or agency) |
parentId | string | — | Parent folder ID to list files within a specific folder |
sortOrder | string | — | Direction to sort files (asc or desc) |
Parameters from the server's own tool schema.
Why get_media_files is rated Low
This tool retrieves or queries data from a media library without side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could enumerate media files, but cannot alter them. Classified as Read with low severity.
From the tool's definition Tool description states 'Get list of files and folders from the media library' — a retrieval operation with no modification or deletion. The verbs 'Get' and 'list' with 'filtering and search capabilities' are characteristic of read-only query operations.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs get_media_files 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 get_media_files, this is the rule to start with:
get_media_files 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 get_media_files call is checked against it from then on.
Questions about get_media_files
Get list of files and folders from the media library with filtering and search capabilities. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_media_files accepts 9 parameters: type, altId, limit, query, offset, sortBy, altType, parentId, 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 get_media_files: 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.
get_media_files 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 get_media_files 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 get_media_files. 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.
get_media_files 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.
This server
Across the catalogue