trigger_create_time_driven · Gworkspace MCP: Risk & Policy

WHAT IT DOES

What trigger_create_time_driven does on Gworkspace

AI agents invoke trigger_create_time_driven to trigger actions in Gworkspace. 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.

WHY IT NEEDS A POLICY

Why trigger_create_time_driven needs a policy

Creating time-driven triggers in Google Apps Script executes external operations automatically and repeatedly. This is an Execute action because it causes code to run at scheduled times with effects dependent on what the trigger targets. It could trigger destructive or financial actions if misconfigured, but the primary classification is Execute.

From the tool's definition Tool name 'trigger_create_time_driven' indicates creation of a time-driven trigger, which executes code or automations on a schedule.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trigger_create_time_driven Rate-limited

trigger_create_time_driven stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "trigger_create_time_driven": {
      "limits": [
        {
          "counter": "trigger_create_time_driven_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about trigger_create_time_driven

What does the trigger_create_time_driven tool do? +

trigger_create_time_driven. It is categorised as a Execute tool in the Gworkspace MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on trigger_create_time_driven? +

Register the Gworkspace MCP server in PolicyLayer and add a rule for trigger_create_time_driven: 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 Gworkspace. Nothing to install.

What risk level is trigger_create_time_driven? +

trigger_create_time_driven is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit trigger_create_time_driven? +

Yes. Add a rate_limit block to the trigger_create_time_driven 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 trigger_create_time_driven completely? +

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

trigger_create_time_driven is provided by the Gworkspace MCP server (leoonic/gworkspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.