# get_responses

Get all responses submitted to a specific survey.

Agent View of the PolicyLayer registry record for `get_responses`. HTML page: https://policylayer.com/tools/com-getinquira-inquira/get-responses

## Facts

- Tool: `get_responses`
- Server: Inquira (`https://getinquira.com/api/mcp`) — https://policylayer.com/tools/com-getinquira-inquira.md
- Homepage: https://github.com/BayarBH/inquira-agent-plugin
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_responses",
    "arguments": {
      "survey_id": "<survey_id>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Inquira:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_responses": {}
  }
}
```

## Other tools on Inquira (5)

- `get_ai_report` — Read — https://policylayer.com/tools/com-getinquira-inquira/get-ai-report.md
- `get_survey_link` — Read — https://policylayer.com/tools/com-getinquira-inquira/get-survey-link.md
- `get_surveys` — Read — https://policylayer.com/tools/com-getinquira-inquira/get-surveys.md
- `create_survey` — Write — https://policylayer.com/tools/com-getinquira-inquira/create-survey.md
- `publish_survey` — Write — https://policylayer.com/tools/com-getinquira-inquira/publish-survey.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getinquira-inquira · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getinquira-inquira