Low Risk

list_script_processes_tool

List recent execution processes for user's scripts.

How to control list_script_processes_tool ↓

What list_script_processes_tool does on Apps Script MCP

AI agents call list_script_processes_tool to retrieve information from Apps Script MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_script_processes_tool needs a policy

This tool queries and returns metadata about past script executions without altering, executing, or deleting any scripts or data. It is a passive audit/monitoring function analogous to checking logs or status. The blast radius of misuse is minimal: an attacker might learn execution history but cannot execute new code, modify scripts, or destroy data.

From the tool's definition Tool name contains 'list' and description states 'List recent execution processes' — a retrieval operation with no modification or side effects.

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

How to control list_script_processes_tool

PolicyLayer is an MCP gateway — it sits between your AI agents and Apps Script MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_script_processes_tool:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_script_processes_tool": {}
  }
}

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

  1. Create a free account and register Apps Script MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_script_processes_tool

What does the list_script_processes_tool tool do? +

List recent execution processes for user's scripts. It is categorised as a Read tool in the Apps Script MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_script_processes_tool? +

Register the Apps Script MCP server in PolicyLayer and add a rule for list_script_processes_tool: 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 Apps Script MCP. Nothing to install.

What risk level is list_script_processes_tool? +

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

Can I rate-limit list_script_processes_tool? +

Yes. Add a rate_limit block to the list_script_processes_tool 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 list_script_processes_tool completely? +

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

list_script_processes_tool is provided by the Apps Script MCP server (sam-ent/google-automation-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Apps Script MCP tool call.

Start from Apps Script MCP, 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.

60 Apps Script MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.