create_input_preset
Create a new input preset (community input) for a workflow. This allows you to share pre-configured input values with others.
This record as markdown: /tools/flowdot-llc-mcp-server/create-input-preset.md
What create_input_preset does on FlowDot MCP Server
AI agents use create_input_preset 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 create_input_preset is rated Medium
This tool creates and stores new input presets in the FlowDot platform, making it a Write operation (reversible data creation). Severity is medium because while the action itself is not destructive, it could potentially pollute shared resources if an agent creates numerous invalid or malicious presets, affecting other users' experience.
From the tool's definition Tool description states 'Create a new input preset' which is a create operation that modifies data. The function allows sharing pre-configured input values, indicating it writes new data to the platform that persists and can be accessed by others.
Attacks that exploit this kind of access
The rule that runs create_input_preset 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 create_input_preset, this is the rule to start with:
create_input_preset 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 create_input_preset call is checked against it from then on.
Questions about create_input_preset
Create a new input preset (community input) for a workflow. This allows you to share pre-configured input values with others. 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 create_input_preset: 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.
create_input_preset 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 create_input_preset 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 create_input_preset. 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.
create_input_preset 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