Google Apps Scriptのライブラリを管理します
AI agents use manage_gas_libraries to create or update resources in Google Apps Script MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Apps Script MCP Server environment.
Library management in GAS involves adding, removing, updating, or modifying library dependencies in a project—these are reversible write operations that change project state.
From the tool's definition Tool name 'manage_gas_libraries' and description 'Google Apps Scriptのライブラリを管理します' (manage Google Apps Script libraries) indicates library management operations that modify the GAS project configuration and dependencies.
Attacks that exploit this kind of access
Google Apps Scriptのライブラリを管理します. It is categorised as a Write tool in the Google Apps Script MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for manage_gas_libraries: 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.
manage_gas_libraries 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 manage_gas_libraries 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 manage_gas_libraries. 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.
manage_gas_libraries 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 →