update_input_preset
Update an existing input preset. You can only update presets you created.
This record as markdown: /tools/flowdot-llc-mcp-server/update-input-preset.md
What update_input_preset does on FlowDot MCP Server
AI agents use update_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 update_input_preset is rated Medium
The tool modifies existing data (input presets) in a reversible manner, fitting the Write category. Severity is medium because changes to presets could affect workflow execution and downstream processes, but the impact is scoped to the user's own presets (as indicated by the ownership restriction "presets you created"). This is not Destructive (irreversible deletion), Execute (arbitrary code execution), or Financial.
From the tool's definition Tool performs an 'update' operation on input presets, which modifies data reversibly. The description explicitly states "Update an existing input preset," indicating data modification rather than creation or deletion.
Attacks that exploit this kind of access
The rule that runs update_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 update_input_preset, this is the rule to start with:
update_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 update_input_preset call is checked against it from then on.
Questions about update_input_preset
Update an existing input preset. You can only update presets you created. 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 update_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.
update_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 update_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 update_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.
update_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