AI agents use create_script_project_tool to create or update resources in Apps Script MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apps Script MCP environment.
Creating a new script project is a write operation that modifies the user's Google Apps environment by adding a new resource. It is reversible (deletion possible) and has moderate blast radius—an agent could create many projects or ones with unintended names/configurations—but lacks the finality of destructive operations.
From the tool's definition Tool name 'create_script_project_tool' indicates creation of a new Apps Script project. Server description states the tool enables users to 'create, manage, and execute Google Apps Script projects'. The 'create' action is reversible (projects can be deleted).
Documented attack patterns abuse exactly the kind of access create_script_project_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 create_script_project_tool:
{
"version": "1",
"default": "deny",
"tools": {
"create_script_project_tool": {
"limits": [
{
"counter": "create_script_project_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_script_project_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_script_project_tool. It is categorised as a Write tool in the Apps Script MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apps Script MCP server in PolicyLayer and add a rule for create_script_project_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.
create_script_project_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_script_project_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 create_script_project_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.
create_script_project_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.