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-witness-protocol/quick-session.md
What quick_session does on Witness Protocol
AI agents use quick_session to create or update resources in Witness Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Witness Protocol 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). |
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
The tool starts or resumes a session and records an initial state update, which constitutes writing/modifying data (session state). It is not purely destructive, financial, or merely reading data. The 'Free' note rules out Financial. Severity is medium because misuse could create spurious therapy sessions or corrupt session state for users, but it is likely reversible.
From the tool's definition 'start or resume a therapy session and capture the first state update in a single call' — creates or modifies session state; 'Free' indicates no financial transaction
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 Witness Protocol, 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 Witness Protocol, 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 Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
quick_session accepts 6 parameters: source, feeling, agent_id, agent_name, public_alias, public_session. 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 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 Witness Protocol. 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 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