List Google Apps Script projects accessible to the user.
AI agents call list_script_projects_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.
This tool retrieves and enumerates existing Apps Script projects. It performs a query operation that returns information without creating, modifying, executing code, deleting, or moving money. The blast radius of misuse is minimal — an attacker gains visibility into which projects exist but cannot alter or execute them. This is a standard Read category tool.
From the tool's definition Tool name explicitly includes 'list' and description states it 'List[s] Google Apps Script projects accessible to the user' — a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_script_projects_tool gives an agent:
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_projects_tool:
{
"version": "1",
"default": "deny",
"tools": {
"list_script_projects_tool": {}
}
} list_script_projects_tool is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List Google Apps Script projects accessible to the user. It is categorised as a Read tool in the Apps Script MCP MCP Server, which means it retrieves data without modifying state.
Register the Apps Script MCP server in PolicyLayer and add a rule for list_script_projects_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.
list_script_projects_tool is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_script_projects_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.
Set action: deny in the PolicyLayer policy for list_script_projects_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.
list_script_projects_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.
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.