This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/typeform-get-responses.md
What typeform_get_responses does on UnClick
AI agents call typeform_get_responses to retrieve information from UnClick 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 |
|---|---|---|---|
limit | number | — | Responses to return (max 1000, default 25) |
since | string | — | ISO 8601 lower bound on submission time |
form_id | string | Yes | Form id |
access_token | string | Yes | Typeform personal access token |
Parameters from the server's own tool schema.
Why typeform_get_responses is rated Low
This tool queries and retrieves data (Typeform responses) without modifying, deleting, or executing external operations. It is a straightforward Read operation with minimal blast radius—an AI agent retrieving form responses poses no risk of data loss, financial harm, or system compromise. The low severity reflects that viewing existing data has limited negative impact.
From the tool's definition Tool name and description indicate retrieval of form submissions: 'Get submissions for a Typeform form.' The verb 'Get' and the lack of any modification language (create, delete, update) clearly indicate a read operation.
Risk signalsHandles credentials or secrets (access_token)
Attacks that exploit this kind of access
The rule that runs typeform_get_responses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For typeform_get_responses, this is the rule to start with:
typeform_get_responses 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 UnClick, apply this rule, and every typeform_get_responses call is checked against it from then on.
Questions about typeform_get_responses
Get submissions for a Typeform form. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
typeform_get_responses accepts 4 parameters: limit, since, form_id, access_token. Required: form_id, access_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for typeform_get_responses: 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 UnClick. Nothing to install.
typeform_get_responses 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 typeform_get_responses 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 typeform_get_responses. 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.
typeform_get_responses is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue