smart_dependency_check · Google Apps Script MCP Server MCP

WHAT IT DOES

What smart_dependency_check does on Google Apps Script MCP Server

AI agents invoke smart_dependency_check 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.

WHY IT NEEDS A POLICY

Why smart_dependency_check needs a policy

The tool both checks (Read) and resolves (Write/Execute) runtime dependencies. Resolving dependencies typically means downloading, installing, or modifying the environment, which constitutes an Execute-level action. The blast radius is medium since a misconfigured dependency resolution could break the project environment, but it is unlikely to cause irreversible data loss.

From the tool's definition 'Check and resolve runtime dependencies' — the word 'resolve' implies active installation or configuration of dependencies, not merely reading

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

smart_dependency_check Rate-limited

smart_dependency_check 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": {
    "smart_dependency_check": {
      "limits": [
        {
          "counter": "smart_dependency_check_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 Google Apps Script MCP Server, so you can run agents against it safely.

FAQ

Questions about smart_dependency_check

What does the smart_dependency_check tool do? +

Check and resolve runtime dependencies. 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.

How do I enforce a policy on smart_dependency_check? +

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

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

Can I rate-limit smart_dependency_check? +

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

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

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