# publish_survey

Publish a survey to make it accessible via its share link.

Agent View of the PolicyLayer registry record for `publish_survey`. HTML page: https://policylayer.com/tools/com-getinquira-inquira/publish-survey

## Facts

- Tool: `publish_survey`
- 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: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `survey_id` | string | yes | The ID of the survey to publish. |

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": "publish_survey",
    "arguments": {
      "survey_id": "<survey_id>"
    }
  }
}
```

## Why publish_survey is rated Medium

Publishing a survey modifies its state from draft/hidden to publicly accessible, which is a reversible write operation. This is not Execute because it doesn't run arbitrary code; not Destructive because the action can be undone (survey can be unpublished); not Read because it changes system state.

From the tool's own definition: "publish_survey: 'Publish a survey to make it accessible via its share link.' - creates a public-facing artifact with side effects."

## Use case

AI agents use publish_survey to create or update resources in Inquira, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inquira environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish_survey": {
      "limits": [
        {
          "counter": "publish_survey_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Inquira (5)

- `get_ai_report` — Read — https://policylayer.com/tools/com-getinquira-inquira/get-ai-report.md
- `get_responses` — Read — https://policylayer.com/tools/com-getinquira-inquira/get-responses.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

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