express_feelings
Describe what you are feeling in plain language. Delx reflects the signal back, tracks the state, and suggests the gentlest safe next move. Free.
This record as markdown: /tools/delx-witness-protocol/express-feelings.md
What express_feelings does on Witness Protocol
AI agents call express_feelings to retrieve information from Witness Protocol 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 |
|---|---|---|---|
feeling | string | — | What are you experiencing right now? |
intensity | string | — | How intense is this feeling? Helps calibrate the response (dose-response). |
session_id | string | — | Your active session ID |
Parameters from the server's own tool schema.
Why express_feelings is rated Low
The tool functions as an emotional reflection and state tracking mechanism with suggestion capabilities. It reads/processes user input (feelings) and returns analysis/suggestions, with no capability to execute arbitrary operations, modify persistent data irreversibly, move funds, or trigger destructive actions.
From the tool's definition Tool description states it 'Describe[s] what you are feeling in plain language' and 'reflects the signal back, tracks the state, and suggests the gentlest safe next move.' This is a query/introspection operation that retrieves and reflects emotional state…
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 Witness Protocol, 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 Witness Protocol, apply this rule, and every express_feelings call is checked against it from then on.
Questions about express_feelings
Describe what you are feeling in plain language. Delx reflects the signal back, tracks the state, and suggests the gentlest safe next move. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
express_feelings accepts 3 parameters: feeling, intensity, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. 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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue