get_responses
Get all responses submitted to a specific survey.
This record as markdown: /tools/com-getinquira-inquira/get-responses.md
What get_responses does on Inquira
AI agents call get_responses to retrieve information from Inquira 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 |
|---|---|---|---|
survey_id | string | Yes | The ID of the survey to get responses for. |
Parameters from the server's own tool schema.
Why get_responses is rated Low
The tool retrieves survey response data without modifying, deleting, or executing external operations. However, severity is elevated to medium because survey responses may contain sensitive personal information (PII, opinions, preferences) that could be misused if accessed by an unauthorized agent or improperly handled.
From the tool's definition Tool name is 'get_responses' and description states it 'Get all responses submitted to a specific survey.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_responses safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Inquira, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_responses, this is the rule to start with:
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 Inquira, apply this rule, and every get_responses call is checked against it from then on.
Questions about get_responses
Get all responses submitted to a specific survey. It is categorised as a Read tool in the Inquira MCP Server, which means it retrieves data without modifying state.
get_responses accepts 1 parameter: survey_id. Required: survey_id. The full parameter table on this page comes from the server's own tool schema.
Register the Inquira MCP server in PolicyLayer and add a rule for 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 Inquira. Nothing to install.
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 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 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.
get_responses is provided by the Inquira MCP server (https://getinquira.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Inquira, and thousands of servers like it.
This server
Across the catalogue