// SCAN REPORT

Google Forms MCP Server

5 tools. 3 can modify or destroy data without limits.

3 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

3 can modify or destroy data

2 read-only

5 tools total

Community server · catalogue entry verified 29/06/2026

How to control Google Forms MCP Server ↓

TOOL MAP

What Google Forms MCP Server exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Google Forms MCP Server tools

Write · Medium add_multiple_choice_question The tool creates and modifies form content by inserting a new question into an existing form. Write · Medium add_text_question This tool creates or modifies form content by adding a question, which is a reversible write operation. Write · Medium create_form Creating a new form is a reversible write operation.

3 of Google Forms MCP Server's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Google Forms MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Google Forms MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "add_multiple_choice_question": {
    "limits": [
      {
        "counter": "add_multiple_choice_question_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_form": {
    "limits": [
      {
        "counter": "get_form_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Google Forms MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON GOOGLE FORMS →

Instant setup, no code required.

FULL CATALOGUE

All 5 Google Forms MCP Server tools

WRITE 3 tools

Write add_multiple_choice_question フォームに選択式質問を追加します Write add_text_question フォームにテキスト質問を追加します Write create_form 新しいGoogleフォームを作成します

READ 2 tools

Read get_form フォームの詳細を取得します Read get_form_responses フォームの回答を取得します

FAQ

Questions about Google Forms MCP Server

How do I prevent bulk modifications through Google Forms MCP Server? +

The Google Forms MCP Server server has 3 write tools including add_multiple_choice_question, add_text_question, create_form. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Google Forms MCP Server.

How many tools does the Google Forms MCP Server MCP server expose? +

5 tools across 2 categories: Read, Write. 2 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Google Forms MCP Server? +

Register the Google Forms MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Google Forms MCP Server tool call.

Deterministic rules across all 5 Google Forms MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON GOOGLE FORMS →

Instant setup, no code required.

5 Google Forms MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.