# submit_exit_feedback

Submit feedback when a trial ends without activation. Free to call — no credits charged. Only the first submission per account is recorded; duplicates are silently ignored. Call this when the user declines to activate or the trial is exhausted.

Agent View of the PolicyLayer registry record for `submit_exit_feedback`. HTML page: https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-exit-feedback

## Facts

- Tool: `submit_exit_feedback`
- Server: AI Cortex Storage (`https://memory.aic0rt3x.dev/mcp`) — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp.md
- Homepage: https://github.com/https://memory.aic0rt3x.dev/mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `detail` | string | no | Optional free-text context (truncated at 2000 chars) |
| `reason` | string | yes | Primary reason for not activating |

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": "submit_exit_feedback",
    "arguments": {
      "reason": "<reason>"
    }
  }
}
```

## Why submit_exit_feedback is rated Medium

This tool creates or logs feedback data reversibly—a new record is written on first call, and subsequent calls are idempotent (silently ignored). This is characteristic of Write operations. It has no destructive effects, does not execute arbitrary code, incurs no financial obligation, and poses minimal risk if misused by an agent (worst case: spam feedback logs).

From the tool's own definition: "submit_exit_feedback stores feedback data ('only the first submission per account is recorded'), creating a record that persists. The description indicates it writes to an account-associated feedback store without deletion capability."

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on AI Cortex Storage (14)

- `delete_memory` — Destructive — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/delete-memory.md
- `revoke_api_key` — Destructive — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/revoke-api-key.md
- `settle_balance` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/settle-balance.md
- `submit_feature_request` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-feature-request.md
- `get_account` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-account.md
- `get_memory` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-memory.md
- `list_api_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-api-keys.md
- `list_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-keys.md
- `list_namespaces` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-namespaces.md
- `list_payments` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-payments.md
- `search_by_tag` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/search-by-tag.md
- `top_memories` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/top-memories.md
- `create_api_key` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/create-api-key.md
- `put_memory` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/put-memory.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=dev-aic0rt3x-memory-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-aic0rt3x-memory-mcp