handle_oauth_callback · Gcalendar MCP: Risk & Policy

WHAT IT DOES

What handle_oauth_callback does on Gcalendar

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

WHY IT NEEDS A POLICY

Why handle_oauth_callback needs a policy

An AI agent can call handle_oauth_callback faster than any human can review — one bad instruction and it creates or modifies resources in Gcalendar by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

handle_oauth_callback Rate-limited

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

FAQ

Questions about handle_oauth_callback

What does the handle_oauth_callback tool do? +

Complete OAuth with authorization code. It is categorised as a Write tool in the Gcalendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on handle_oauth_callback? +

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

What risk level is handle_oauth_callback? +

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

Can I rate-limit handle_oauth_callback? +

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

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

handle_oauth_callback is provided by the Gcalendar MCP server (sandeepmallareddy/gcalendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.