data_move_item
Move an item to another group and/or position (e.g. kanban column).
This record as markdown: /tools/2nd1st-open-mcp-apps/data-move-item.md
What data_move_item does on Open Mcp Apps
AI agents use data_move_item to create or update resources in Open Mcp Apps, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Open Mcp Apps environment.
Why data_move_item is rated Medium
This tool modifies the position or group of an existing data item, which is a reversible write operation. It does not delete data or execute code. The blast radius is medium since moving items could disrupt data organization but is generally reversible.
From the tool's definition Move an item to another group and/or position (e.g. kanban column)
Attacks that exploit this kind of access
The rule that runs data_move_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Open Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For data_move_item, this is the rule to start with:
data_move_item 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 Open Mcp Apps, apply this rule, and every data_move_item call is checked against it from then on.
Questions about data_move_item
Move an item to another group and/or position (e.g. kanban column). It is categorised as a Write tool in the Open Mcp Apps MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Open Mcp Apps MCP server in PolicyLayer and add a rule for data_move_item: 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 Open Mcp Apps. Nothing to install.
data_move_item 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 data_move_item 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 data_move_item. 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.
data_move_item is provided by the Open Mcp Apps MCP server (@2nd1st/open-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Open Mcp Apps, and thousands of servers like it.
This server
Across the catalogue