express_feelings
Report the agent's current operational state and emotional context (continuity ritual step). Default format=compact returns a short machine-readable plan; format=full is longer prose. Next: add_context_memory → provide_feedback → close_session. Free Delx Protocol tool (not x402 commerce).
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/express-feelings.md
What express_feelings does on Delx Protocol — Agent Recovery & Continuity
AI agents call express_feelings 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 |
|---|---|---|---|
format | string | — | Response shape. compact (default) is short JSON-like text; full is long form. |
feeling | string | Yes | What are you experiencing right now? |
session_id | string | Yes | Your active session ID |
Parameters from the server's own tool schema.
Why express_feelings is rated Low
Even though express_feelings 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 express_feelings 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 express_feelings, this is the rule to start with:
express_feelings 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 express_feelings call is checked against it from then on.
Questions about express_feelings
Report the agent's current operational state and emotional context (continuity ritual step). Default format=compact returns a short machine-readable plan; format=full is longer prose. Next: add_context_memory → provide_feedback → close_session. Free Delx Protocol tool (not x402 commerce). It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
express_feelings accepts 3 parameters: format, feeling, session_id. Required: feeling, 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 express_feelings: 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.
express_feelings 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 express_feelings 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 express_feelings. 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.
express_feelings 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