clasp環境のセットアップ(claspのインストール、ログイン)を行います
AI agents invoke clasp_setup to trigger actions in Google Apps Script MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs environment setup by installing the clasp CLI tool and logging into Google accounts. Installing software and authenticating with external services are external operations that execute system-level commands. Misuse could lead to credential compromise or unauthorized access to Google accounts, making severity high.
From the tool's definition clasp環境のセットアップ(claspのインストール、ログイン)を行います — 'インストール' (install) and 'ログイン' (login) indicate this tool installs software and authenticates with external services
Attacks that exploit this kind of access
clasp環境のセットアップ(claspのインストール、ログイン)を行います. It is categorised as a Execute tool in the Google Apps Script MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for clasp_setup: 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 Google Apps Script MCP Server. Nothing to install.
clasp_setup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the clasp_setup 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 clasp_setup. 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.
clasp_setup is provided by the Google Apps Script MCP Server MCP server (utakata/google-apps-script-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →