This record as markdown: /tools/ghl/get-csv-upload-status.md
What get_csv_upload_status does on Ghl
AI agents call get_csv_upload_status 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 |
|---|---|---|---|
skip | number | — | Number to skip |
limit | number | — | Number to return |
userId | string | — | Filter by user ID |
includeUsers | boolean | — | Include user data |
Parameters from the server's own tool schema.
Why get_csv_upload_status is rated Low
This tool queries the state of uploaded CSV files without creating, modifying, or deleting any data. It is a simple status check operation with no side effects, fitting the Read category definition of retrieving or querying data. The blast radius of misuse is minimal—an agent could only gain visibility into upload progress, not affect any actual data or workflows.
From the tool's definition Tool name and description indicate a status retrieval operation: 'Get status of CSV uploads'. The verb 'get' and the object 'status' clearly indicate a read operation with no data modification.
Attacks that exploit this kind of access
The rule that runs get_csv_upload_status 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_csv_upload_status, this is the rule to start with:
get_csv_upload_status 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_csv_upload_status call is checked against it from then on.
Questions about get_csv_upload_status
Get status of CSV uploads. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
get_csv_upload_status accepts 4 parameters: skip, limit, userId, includeUsers. 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_csv_upload_status: 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_csv_upload_status 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_csv_upload_status 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_csv_upload_status. 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_csv_upload_status 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