set_secure_property · Google Apps Script MCP Server MCP

WHAT IT DOES

What set_secure_property does on Google Apps Script MCP Server

AI agents use set_secure_property 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.

WHY IT NEEDS A POLICY

Why set_secure_property needs a policy

This tool creates or modifies script properties with encryption. While it handles sensitive data (secrets/credentials), the operation itself is reversible—properties can be updated or deleted. It does not execute code, delete data irreversibly, or move money. The encryption layer reduces runtime risk but does not change the fundamental category.

From the tool's definition Tool name 'set_secure_property' and description indicate data storage/modification ('安全に保存します' = 'safely store'). The tool writes encrypted data to script properties, which is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_secure_property Rate-limited

set_secure_property 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_secure_property": {
      "limits": [
        {
          "counter": "set_secure_property_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Apps Script MCP Server, so you can run agents against it safely.

FAQ

Questions about set_secure_property

What does the set_secure_property tool do? +

🔒 スクリプトプロパティに暗号化してデータを安全に保存します. 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.

How do I enforce a policy on set_secure_property? +

Register the Google Apps Script MCP Server MCP server in PolicyLayer and add a rule for set_secure_property: 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.

What risk level is set_secure_property? +

set_secure_property is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_secure_property? +

Yes. Add a rate_limit block to the set_secure_property 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.

How do I block set_secure_property completely? +

Set action: deny in the PolicyLayer policy for set_secure_property. 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.

What MCP server provides set_secure_property? +

set_secure_property 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.