# list_submissions

List submissions for one of your forms. Returns counts + per-submission metadata by default; set includeContent to include message bodies (third-party PII). Errors with: unauthorized, not_found, forbidden. Requires a full-access token.

Agent View of the PolicyLayer registry record for `list_submissions`. HTML page: https://policylayer.com/tools/com-formpaste-formpaste/list-submissions

## Facts

- Tool: `list_submissions`
- Server: Formpaste (`formpaste-mcp`) — https://policylayer.com/tools/com-formpaste-formpaste.md
- Install: `npx -y formpaste-mcp`
- Homepage: https://github.com/webrating/formpaste-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 4 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `limit` | number | no | Maximum number of submissions to return. |
| `folder` | string | no | Which folder to list. Defaults to inbox. |
| `formId` | string | yes | A form id from create_form or list_forms, e.g. frm_... |
| `includeContent` | boolean | no | Include full submission message bodies (third-party PII). Defaults to false. |

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": "list_submissions",
    "arguments": {
      "formId": "<formId>"
    }
  }
}
```

## Why list_submissions is rated Low

This tool queries and retrieves submission data from forms—a read-only operation with no side effects. The severity is medium rather than low because the data may contain PII (personally identifiable information) as the description acknowledges, creating a data exposure risk if an agent misuses the full-access token requirement or includeContent flag.

From the tool's own definition: "Tool name is 'list_submissions' and description says 'List submissions' which retrieves data. Description explicitly notes it 'Returns counts + per-submission metadata by default' and optionally 'include[s] message bodies'."

Risk signals: Accepts file system path (folder)

## Use case

AI agents call list_submissions to retrieve information from Formpaste 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 Formpaste:

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

## Other tools on Formpaste (5)

- `get_form` — Read — https://policylayer.com/tools/com-formpaste-formpaste/get-form.md
- `get_snippet` — Read — https://policylayer.com/tools/com-formpaste-formpaste/get-snippet.md
- `list_forms` — Read — https://policylayer.com/tools/com-formpaste-formpaste/list-forms.md
- `create_form` — Write — https://policylayer.com/tools/com-formpaste-formpaste/create-form.md
- `send_test_submission` — Write — https://policylayer.com/tools/com-formpaste-formpaste/send-test-submission.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-formpaste-formpaste · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-formpaste-formpaste