toggle_community_inputs
Enable or disable community inputs (input presets) for a workflow. When enabled, users can create and share pre-configured input values for the workflow. Only the workflow owner can change this setting.
This record as markdown: /tools/flowdot-llc-mcp-server/toggle-community-inputs.md
What toggle_community_inputs does on FlowDot MCP Server
AI agents use toggle_community_inputs to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why toggle_community_inputs is rated Medium
This tool creates or modifies workflow configuration state (toggling a feature flag). It is reversible—the setting can be toggled back on or off. While it affects workflow visibility and sharing behavior, it does not delete data, execute arbitrary code, or move money. It is Write rather than Execute because it changes a bounded configuration setting, not triggers arbitrary external operations.
From the tool's definition Tool enables or disables community inputs for workflows, modifying workflow configuration settings. Description states 'Enable or disable community inputs' and 'Only the workflow owner can change this setting,' indicating a reversible modification of workflow…
Attacks that exploit this kind of access
The rule that runs toggle_community_inputs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For toggle_community_inputs, this is the rule to start with:
toggle_community_inputs 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 FlowDot MCP Server, apply this rule, and every toggle_community_inputs call is checked against it from then on.
Questions about toggle_community_inputs
Enable or disable community inputs (input presets) for a workflow. When enabled, users can create and share pre-configured input values for the workflow. Only the workflow owner can change this setting. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for toggle_community_inputs: 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 FlowDot MCP Server. Nothing to install.
toggle_community_inputs 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 toggle_community_inputs 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 toggle_community_inputs. 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.
toggle_community_inputs is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue