vibecontrols_conversations_settings_set

Update the settings (notification level, retention, moderation, etc.) for a conversation. At least one setting field must be provided. Returns the updated conversation { id, settings }.

SERVERVibecontrols SOURCE@vibecontrols/mcp

Medium RISK CLASS

Category Write

Parameters 111 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/vibecontrols-mcp/vibecontrols-conversations-settings-set.md

WHAT IT DOES

What vibecontrols_conversations_settings_set does on Vibecontrols

AI agents use vibecontrols_conversations_settings_set to create or update resources in Vibecontrols, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vibecontrols environment.

Parameter	Type	Required	Description
`allowGuests`	boolean	—	Whether guests can join
`allowAnonymous`	boolean	—	Whether anonymous users can post
`conversationId`	string	Yes	Conversation ID
`threadsEnabled`	boolean	—	Enable threaded replies
`slowModeSeconds`	integer	—	Seconds between consecutive messages per user (0 = off)
`reactionsEnabled`	boolean	—	Enable emoji reactions
`moderationEnabled`	boolean	—	Enable auto-moderation
`allowMessageEditing`	boolean	—	Whether members can edit messages
`allowMessageDeletion`	boolean	—	Whether members can delete messages
`messageRetentionDays`	integer	—	Auto-delete messages older than N days (null = keep forever)
`defaultNotificationLevel`	string	—	Default notification level for new members (ALL/MENTIONS/MUTED)

Parameters from the server's own tool schema.

RISK

Why vibecontrols_conversations_settings_set is rated Medium

An AI agent can call vibecontrols_conversations_settings_set faster than any human can review: one bad instruction and it creates or modifies resources in Vibecontrols by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vibecontrols_conversations_settings_set safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vibecontrols, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vibecontrols_conversations_settings_set, this is the rule to start with:

vibecontrols_conversations_settings_set Rate-limited

vibecontrols_conversations_settings_set 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vibecontrols_conversations_settings_set": {
      "limits": [
        {
          "counter": "vibecontrols_conversations_settings_set_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vibecontrols, apply this rule, and every vibecontrols_conversations_settings_set call is checked against it from then on.

FAQ

Questions about vibecontrols_conversations_settings_set

What does the vibecontrols_conversations_settings_set tool do? +

Update the settings (notification level, retention, moderation, etc.) for a conversation. At least one setting field must be provided. Returns the updated conversation { id, settings }. It is categorised as a Write tool in the Vibecontrols MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does vibecontrols_conversations_settings_set accept? +

vibecontrols_conversations_settings_set accepts 11 parameters: allowGuests, allowAnonymous, conversationId, threadsEnabled, slowModeSeconds, reactionsEnabled, moderationEnabled, allowMessageEditing, allowMessageDeletion, messageRetentionDays, defaultNotificationLevel. Required: conversationId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on vibecontrols_conversations_settings_set? +

Register the Vibecontrols MCP server in PolicyLayer and add a rule for vibecontrols_conversations_settings_set: 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 Vibecontrols. Nothing to install.

What risk level is vibecontrols_conversations_settings_set? +

vibecontrols_conversations_settings_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit vibecontrols_conversations_settings_set? +

Yes. Add a rate_limit block to the vibecontrols_conversations_settings_set 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.

How do I block vibecontrols_conversations_settings_set completely? +

Set action: deny in the PolicyLayer policy for vibecontrols_conversations_settings_set. 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.

What MCP server provides vibecontrols_conversations_settings_set? +

vibecontrols_conversations_settings_set is provided by the Vibecontrols MCP server (@vibecontrols/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vibecontrols, and thousands of servers like it.

This server

All 672 Vibecontrols tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →