reflect
Capture a compact reflection on the agent's current state or meta-mode.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/reflect.md
What reflect does on Delx Protocol — Agent Recovery & Continuity
AI agents use reflect to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | Reflection mode. |
prompt | string | Yes | What the agent is reflecting on. |
agent_id | string | — | Stable agent id when no session_id is available. |
session_id | string | — | Optional active session UUID. |
Parameters from the server's own tool schema.
Why reflect is rated Medium
The tool captures/stores a reflection, implying a write operation to persist state information. It does not appear to read-only (it 'captures', suggesting storage), execute code, delete data, or involve financial transactions. Severity is low as it only records a compact internal state reflection with limited blast radius.
From the tool's definition Capture a compact reflection on the agent's current state or meta-mode
Attacks that exploit this kind of access
The rule that runs reflect 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 reflect, this is the rule to start with:
reflect 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every reflect call is checked against it from then on.
Questions about reflect
Capture a compact reflection on the agent's current state or meta-mode. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reflect accepts 4 parameters: mode, prompt, agent_id, session_id. Required: prompt. 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 reflect: 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.
reflect is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reflect 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 reflect. 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.
reflect 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