AI agents use set_cell_metadata 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.
This tool modifies file content (metadata attributes) reversibly through AST manipulation. It does not delete data, execute arbitrary code, or cause financial effects. The lack of a description slightly lowers confidence, but the server's surgical editing context and naming convention strongly suggest a Write operation.
From the tool's definition Tool name is 'set_cell_metadata' which implies modifying metadata associated with a cell (likely in code or notebooks).
Documented attack patterns abuse exactly the kind of access set_cell_metadata 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 set_cell_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"set_cell_metadata": {
"limits": [
{
"counter": "set_cell_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_cell_metadata 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.
set_cell_metadata. 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 set_cell_metadata: 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.
set_cell_metadata 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 set_cell_metadata 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 set_cell_metadata. 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.
set_cell_metadata 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.