script_list

THE RISK

Low Risk

Why script_list needs a policy

This tool retrieves and enumerates existing scripts without modifying, deleting, executing, or creating any resources. It is purely informational, making it a Read category tool. Severity is low because listing available scripts poses minimal risk; an AI agent cannot cause harm by discovering what scripts exist in the system.

From the tool's definition Tool name 'script_list' combined with description 'List and discover available scripts' indicates a query/retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access script_list gives an agent:

POLICY

How to control script_list

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_list:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "script_list": {}
  }
}

script_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register ScriptFlow MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More ScriptFlow MCP Server tools

Destructive script_rm Remove a script from the repository Execute script_run Execute a script by name Write script_add Add a new script to the repository Write script_edit Edit an existing script Read script_get Get detailed information about a specific script

All 6 ScriptFlow MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about script_list

What does the script_list tool do? +

List and discover available scripts. It is categorised as a Read tool in the ScriptFlow MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on script_list? +

Register the ScriptFlow MCP Server MCP server in PolicyLayer and add a rule for script_list: 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.

What risk level is script_list? +

script_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit script_list? +

Yes. Add a rate_limit block to the script_list 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.

How do I block script_list completely? +

Set action: deny in the PolicyLayer policy for script_list. 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.

What MCP server provides script_list? +

script_list 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.

Enforce policy on every ScriptFlow MCP Server tool call.

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.

CHECK YOUR STACK →