ghl_get_survey_submissions
Retrieve survey submissions with advanced filtering and pagination. Get responses from contacts who have completed surveys.
This record as markdown: /tools/ghl/ghl-get-survey-submissions.md
What ghl_get_survey_submissions does on Ghl
AI agents call ghl_get_survey_submissions 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 |
|---|---|---|---|
q | string | — | Search by contact ID, name, email, or phone number |
page | number | — | Page number for pagination (default: 1) |
endAt | string | — | End date for filtering submissions (YYYY-MM-DD format) |
limit | number | — | Number of submissions per page (max: 100, default: 20) |
startAt | string | — | Start date for filtering submissions (YYYY-MM-DD format) |
surveyId | string | — | Filter submissions by specific survey ID |
locationId | string | — | The location ID to get submissions for. If not provided, uses the default location from configuration. |
Parameters from the server's own tool schema.
Why ghl_get_survey_submissions is rated Low
This tool queries and retrieves existing survey submission data without any capability to modify, delete, or execute operations. It supports filtering and pagination for data retrieval only, making it a straightforward Read category tool with low severity and blast radius.
From the tool's definition Tool description explicitly states 'Retrieve survey submissions' and 'Get responses from contacts who have completed surveys.' The verb 'Retrieve' and 'Get' with no mention of modification, deletion, or execution indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs ghl_get_survey_submissions 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 ghl_get_survey_submissions, this is the rule to start with:
ghl_get_survey_submissions 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 ghl_get_survey_submissions call is checked against it from then on.
Questions about ghl_get_survey_submissions
Retrieve survey submissions with advanced filtering and pagination. Get responses from contacts who have completed surveys. It is categorised as a Read tool in the Ghl MCP Server, which means it retrieves data without modifying state.
ghl_get_survey_submissions accepts 7 parameters: q, page, endAt, limit, startAt, surveyId, locationId. 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 ghl_get_survey_submissions: 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.
ghl_get_survey_submissions 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 ghl_get_survey_submissions 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 ghl_get_survey_submissions. 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.
ghl_get_survey_submissions 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