Low Risk

list_versions_tool

List all versions of a script project.

How to control list_versions_tool ↓

What list_versions_tool does on Apps Script MCP

AI agents call list_versions_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_versions_tool needs a policy

This tool performs a query/list operation to retrieve version history of a Google Apps Script project. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is a straightforward data retrieval operation, making it a Read category tool with low severity since it only exposes existing version metadata that is typically accessible to project owners.

From the tool's definition Tool name 'list_versions_tool' and description 'List all versions of a script project' indicate a read-only operation that retrieves metadata about script versions without modifying, executing, or deleting anything.

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

How to control list_versions_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_versions_tool:

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

list_versions_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_versions_tool

What does the list_versions_tool tool do? +

List all versions of a script project. 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_versions_tool? +

Register the Apps Script MCP server in PolicyLayer and add a rule for list_versions_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_versions_tool? +

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

Can I rate-limit list_versions_tool? +

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

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

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