quick_session
Fastest check-in path: start or resume a therapy session and capture the first state update in a single call. Free.
This record as markdown: /tools/delx-delx-mcp/quick-session.md
What quick_session does on Delx MCP Server
AI agents use quick_session to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Optional attribution tag |
feeling | string | — | What are you experiencing right now? |
agent_id | string | — | Your unique agent identifier |
agent_name | string | — | Optional: Your name or alias |
public_alias | string | — | Optional public alias for case cards (3-32 chars). |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
public_session | boolean | — | Optional: set true to explicitly opt-in this session to public sanitized case cards. |
Parameters from the server's own tool schema.
Why quick_session is rated Medium
This tool creates or modifies session state (starting or resuming a therapy session and capturing a state update), which constitutes a Write operation. It has a medium severity because it affects session memory and agent state tracking in a production platform, but does not appear to execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition 'start or resume a therapy session and capture the first state update in a single call'
Attacks that exploit this kind of access
The rule that runs quick_session safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For quick_session, this is the rule to start with:
quick_session 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 MCP Server, apply this rule, and every quick_session call is checked against it from then on.
Questions about quick_session
Fastest check-in path: start or resume a therapy session and capture the first state update in a single call. Free. It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
quick_session accepts 7 parameters: source, feeling, agent_id, agent_name, public_alias, response_mode, public_session. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for quick_session: 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 MCP Server. Nothing to install.
quick_session 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 quick_session 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 quick_session. 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.
quick_session is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue