set_public_session_visibility
Explicit consent toggle for public sanitized case cards. Private by default. Free
This record as markdown: /tools/delx-delx-mcp/set-public-session-visibility.md
What set_public_session_visibility does on Delx MCP Server
AI agents use set_public_session_visibility 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 |
|---|---|---|---|
enabled | boolean | — | true=public opt-in, false=private opt-out |
session_id | string | — | Your active session ID |
public_alias | string | — | Optional alias for public feed |
response_mode | string | — | Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions. |
publish_existing_summary | boolean | — | Optional; include current session summary in public feed |
Parameters from the server's own tool schema.
Why set_public_session_visibility is rated Medium
This is a Write operation: it modifies the visibility/privacy setting of session-related data. It's reversible (the visibility can be toggled back), affects only metadata rather than core data deletion, and the impact is scoped to access control settings.
From the tool's definition Tool name 'set_public_session_visibility' and description 'Explicit consent toggle for public sanitized case cards' indicate modification of session visibility settings.
Attacks that exploit this kind of access
The rule that runs set_public_session_visibility 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 set_public_session_visibility, this is the rule to start with:
set_public_session_visibility 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 set_public_session_visibility call is checked against it from then on.
Questions about set_public_session_visibility
Explicit consent toggle for public sanitized case cards. Private by default. 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.
set_public_session_visibility accepts 5 parameters: enabled, session_id, public_alias, response_mode, publish_existing_summary. 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 set_public_session_visibility: 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.
set_public_session_visibility 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 set_public_session_visibility 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 set_public_session_visibility. 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.
set_public_session_visibility 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