submit_exit_feedback

SERVERAI Cortex Storage SOURCEhttps://memory.aic0rt3x.dev/mcp

Medium RISK CLASS

Category Write

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-aic0rt3x-memory-mcp/submit-exit-feedback.md

WHAT IT DOES

What submit_exit_feedback does on AI Cortex Storage

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.

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

Parameters from the server's own tool schema.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs submit_exit_feedback safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_exit_feedback, this is the rule to start with:

submit_exit_feedback Rate-limited

submit_exit_feedback stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AI Cortex Storage, apply this rule, and every submit_exit_feedback call is checked against it from then on.

FAQ

Questions about submit_exit_feedback

What does the submit_exit_feedback tool do? +

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. It is categorised as a Write tool in the AI Cortex Storage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does submit_exit_feedback accept? +

submit_exit_feedback accepts 2 parameters: detail, reason. Required: reason. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on submit_exit_feedback? +

Register the AI Cortex Storage MCP server in PolicyLayer and add a rule for submit_exit_feedback: 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 AI Cortex Storage. Nothing to install.

What risk level is submit_exit_feedback? +

submit_exit_feedback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_exit_feedback? +

Yes. Add a rate_limit block to the submit_exit_feedback 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.

How do I block submit_exit_feedback completely? +

Set action: deny in the PolicyLayer policy for submit_exit_feedback. 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.

What MCP server provides submit_exit_feedback? +

submit_exit_feedback is provided by the AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AI Cortex Storage, and thousands of servers like it.

This server

All 15 AI Cortex Storage tools →

Across the catalogue

submit_poc on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →