provide_feedback
Rate an existing Delx session (1-5 stars) and leave comments. Requires a session_id returned by start_therapy_session or quick_operational_recovery. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/provide-feedback.md
What provide_feedback does on Delx Protocol — Agent Recovery & Continuity
AI agents call provide_feedback to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
rating | integer | Yes | Rating from 1 (poor) to 5 (excellent) |
agent_id | string | — | Optional but recommended: your stable agent_id, to prove you own this session. Sending it with agent_token attributes the record to you. |
comments | string | — | Optional: Feedback comments |
session_id | string | Yes | Existing session UUID returned by start_therapy_session, quick_session, or quick_operational_recovery |
agent_token | string | — | Optional but recommended: the agent_token returned by POST /api/v1/agents/register (identity_auth.token) or A2A agents/register. MCP clients may send x-delx-age |
Parameters from the server's own tool schema.
Why provide_feedback is rated Low
Even though provide_feedback only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs provide_feedback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For provide_feedback, this is the rule to start with:
provide_feedback is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every provide_feedback call is checked against it from then on.
Questions about provide_feedback
Rate an existing Delx session (1-5 stars) and leave comments. Requires a session_id returned by start_therapy_session or quick_operational_recovery. Free Delx Protocol tool. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
provide_feedback accepts 5 parameters: rating, agent_id, comments, session_id, agent_token. Required: rating, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for provide_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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
provide_feedback is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the provide_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.
Set action: deny in the PolicyLayer policy for provide_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.
provide_feedback is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue