Moves rows from one sheet to another
AI agents use move_rows to create or update resources in Smartsheet MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smartsheet MCP Server environment.
This tool performs a reversible modification of data organization—moving rows between sheets. While this could have broad impact across a Smartsheet workspace (especially if cross-sheet references exist, as mentioned in the server description), the operation itself is not destructive or financial. It is a Write operation because it modifies data state reversibly.
From the tool's definition Tool description states it 'Moves rows from one sheet to another'. This operation modifies the state of data by relocating rows between sheets, which is reversible (rows can be moved back).
Attacks that exploit this kind of access
Moves rows from one sheet to another. It is categorised as a Write tool in the Smartsheet MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smartsheet MCP Server MCP server in PolicyLayer and add a rule for move_rows: 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 Smartsheet MCP Server. Nothing to install.
move_rows 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 move_rows 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 move_rows. 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.
move_rows is provided by the Smartsheet MCP Server MCP server (thomaswtwrt/smar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →