google_drive_manage_file · ContextCore MCP: Risk & Policy

WHAT IT DOES

What google_drive_manage_file does on ContextCore MCP

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

WHY IT NEEDS A POLICY

Why google_drive_manage_file needs a policy

The tool name indicates file management on Google Drive, which is a Write operation (create/modify data). Without a description, the confidence is moderate rather than high. Given the sibling tools include both read (google_sheet_get_data) and write (google_sheet_write_data, google_calendar_create_events) operations, this tool likely performs reversible modifications.

From the tool's definition Tool name 'google_drive_manage_file' suggests file management capabilities on Google Drive. No description provided, but 'manage' typically implies create, update, or modify operations on files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

google_drive_manage_file Rate-limited

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

FAQ

Questions about google_drive_manage_file

What does the google_drive_manage_file tool do? +

google_drive_manage_file. It is categorised as a Write tool in the ContextCore MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on google_drive_manage_file? +

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

What risk level is google_drive_manage_file? +

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

Can I rate-limit google_drive_manage_file? +

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

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

google_drive_manage_file is provided by the ContextCore MCP server (rkpraveendev/contextcore-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.