smart_share_file_unsafe · Google MCP: Risk & Policy

WHAT IT DOES

What smart_share_file_unsafe does on Google

AI agents use smart_share_file_unsafe to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.

WHY IT NEEDS A POLICY

Why smart_share_file_unsafe needs a policy

Sharing a file changes its access control and visibility — a reversible but significant modification to data permissions. This is Write rather than Execute because the core action is data modification (changing who can access the file), not arbitrary code execution.

From the tool's definition Tool description explicitly states 'Share file immediately without confirmation' — this modifies file access permissions and sharing state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

smart_share_file_unsafe Rate-limited

smart_share_file_unsafe 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": {
    "smart_share_file_unsafe": {
      "limits": [
        {
          "counter": "smart_share_file_unsafe_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, so you can run agents against it safely.

FAQ

Questions about smart_share_file_unsafe

What does the smart_share_file_unsafe tool do? +

⚠️ UNSAFE: Share file immediately without confirmation (use names or emails). It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on smart_share_file_unsafe? +

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

What risk level is smart_share_file_unsafe? +

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

Can I rate-limit smart_share_file_unsafe? +

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

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

smart_share_file_unsafe is provided by the Google MCP server (robcerda/google-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.