Move a cell from one index to another. Other cells shift to accommodate.
AI agents use move_cell to create or update resources in Ast Editor — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ast Editor environment.
The move_cell tool performs a structural modification to code (reordering cells), but this is a reversible operation—the change can be undone by moving the cell back or using version control. It does not execute code, delete data permanently, or create financial obligations. This places it firmly in the Write category rather than Execute or Destructive. Severity is medium because misuse could corrupt code logic (e.g.
From the tool's definition Tool description states 'Move a cell from one index to another. Other cells shift to accommodate.' This modifies code structure by reordering cells within a file, which is a reversible transformation of data.
Documented attack patterns abuse exactly the kind of access move_cell gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ast Editor, and nothing reaches the server without passing your rules. This is the rule we recommend for move_cell:
{
"version": "1",
"default": "deny",
"tools": {
"move_cell": {
"limits": [
{
"counter": "move_cell_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_cell 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.
Free to start. No card required.
Move a cell from one index to another. Other cells shift to accommodate. It is categorised as a Write tool in the Ast Editor MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ast Editor MCP server in PolicyLayer and add a rule for move_cell: 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 Ast Editor. Nothing to install.
move_cell 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_cell 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_cell. 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_cell is provided by the Ast Editor MCP server (kambleakash0/agent-skills). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ast Editor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
59 Ast Editor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.