// SCAN REPORT

ScriptFlow MCP Server

6 tools. 4 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

4 can modify or destroy data

2 read-only

6 tools total

Community server · catalogue entry verified 12/06/2026

How to control ScriptFlow MCP Server ↓

TOOL MAP

What ScriptFlow MCP Server exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous ScriptFlow MCP Server tools

Destructive · High script_rm This tool deletes scripts that are stored in a persistent repository and version-controlled system. Execute · High script_run The tool's primary function is to execute arbitrary scripts. Write · High script_add This tool creates new executable scripts that can be run by script_run. Write · High script_edit This tool modifies scripts persistently but reversibly—the change can be undone by editing again.

4 of ScriptFlow MCP Server's 6 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control ScriptFlow MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and ScriptFlow MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "script_rm": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "script_add": {
    "limits": [
      {
        "counter": "script_add_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "script_get": {
    "limits": [
      {
        "counter": "script_get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register ScriptFlow MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SCRIPTFLOW →

Free to start. No card required.

FULL CATALOGUE

All 6 ScriptFlow MCP Server tools

DESTRUCTIVE 1 tools

Destructive script_rm Remove a script from the repository

EXECUTE 1 tools

Execute script_run Execute a script by name

WRITE 2 tools

Write script_add Add a new script to the repository Write script_edit Edit an existing script

READ 2 tools

Read script_get Get detailed information about a specific script Read script_list List and discover available scripts

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about ScriptFlow MCP Server

Can an AI agent delete data through the ScriptFlow MCP Server MCP server? +

Yes. The ScriptFlow MCP Server server exposes 1 destructive tools including script_rm. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through ScriptFlow MCP Server? +

The ScriptFlow MCP Server server has 2 write tools including script_add, script_edit. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach ScriptFlow MCP Server.

How many tools does the ScriptFlow MCP Server MCP server expose? +

6 tools across 4 categories: Destructive, Execute, Read, Write. 2 are read-only. 4 can modify, create, or delete data.

How do I enforce a policy on ScriptFlow MCP Server? +

Register the ScriptFlow MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every ScriptFlow MCP Server tool call.

Deterministic rules across all 6 ScriptFlow MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SCRIPTFLOW →

Free to start. No card required.

6 ScriptFlow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.