Copies rows from one sheet to another
AI agents use copy_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.
The tool creates or duplicates data across sheets, which is a Write operation. It does not permanently delete data (not Destructive), does not execute arbitrary code or commands (not Execute), and does not involve financial transactions (not Financial). The severity is medium because copying rows to an unauthorized sheet could expose sensitive data or disrupt workflow, but the operation is reversible via deletion.
From the tool's definition Tool name is 'copy_rows' with description 'Copies rows from one sheet to another' — a reversible operation that creates new data in a destination sheet.
Attacks that exploit this kind of access
Copies 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 copy_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.
copy_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 copy_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 copy_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.
copy_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 →