Copy a range of lines and insert the copy after a given line number. Original lines are preserved. Use with move_lines to reorganise content without rewriting. Only works within allowed directories.
AI agents use copy_lines to create or update resources in FilesystemMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FilesystemMCP environment.
This tool modifies files by inserting copied content, making it a Write operation (reversible modification). It does not delete or permanently alter existing lines, so it is not Destructive.
From the tool's definition Tool description states it will 'Copy a range of lines and insert the copy after a given line number', which creates new data within a file by duplicating existing content.
Attacks that exploit this kind of access
Copy a range of lines and insert the copy after a given line number. Original lines are preserved. Use with move_lines to reorganise content without rewriting. Only works within allowed directories. It is categorised as a Write tool in the FilesystemMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Filesystem MCP server in PolicyLayer and add a rule for copy_lines: 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 FilesystemMCP. Nothing to install.
copy_lines 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_lines 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_lines. 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_lines is provided by the Filesystem MCP server (rijadalisic/filesystemmcp). 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 →