アカウントに紐づくGoogle Apps Scriptプロジェクトの一覧を表示します
AI agents call clasp_list to retrieve information from Google Apps Script MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about existing Google Apps Script projects associated with an account. It performs no modifications, deletions, or side effects—it only lists/retrieves data. This is a classic Read operation with minimal blast radius if misused by an AI agent (at worst, it reveals project names and IDs).
From the tool's definition Tool description: 'アカウントに紐づくGoogle Apps Scriptプロジェクトの一覧を表示します' (Display a list of Google Apps Script projects linked to the account). The verb '一覧を表示' means 'display a list', indicating retrieval and enumeration of existing projects without modification.
Attacks that exploit this kind of access
アカウントに紐づくGoogle Apps Scriptプロジェクトの一覧を表示します. It is categorised as a Read tool in the Google Apps Script MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for clasp_list: 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_list 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 clasp_list 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_list. 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_list 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 →