AI agents call script_rm to permanently remove resources in ScriptFlow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes scripts that are stored in a persistent repository and version-controlled system. Once removed, the script cannot be recovered unless explicitly backed up or version-controlled recovery is available. Deletion of repository artifacts is destructive.
From the tool's definition Tool name 'script_rm' and description 'Remove a script from the repository' indicate irreversible deletion of stored scripts. The verb 'Remove' combined with repository persistence makes this an undoable destructive action.
Documented attack patterns abuse exactly the kind of access script_rm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScriptFlow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for script_rm:
{
"version": "1",
"default": "deny",
"hide": [
"script_rm"
]
}script_rm disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a script from the repository. It is categorised as a Destructive tool in the ScriptFlow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ScriptFlow MCP Server MCP server in PolicyLayer and add a rule for script_rm: 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 ScriptFlow MCP Server. Nothing to install.
script_rm is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the script_rm 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 script_rm. 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.
script_rm is provided by the ScriptFlow MCP Server MCP server (yanmxa/scriptflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScriptFlow MCP Server, 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.
6 ScriptFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.