Read the structure and questions of a Google Form.
AI agents call readForm to retrieve information from Google Workspace MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves data (form structure and questions) with no side effects, reversible operations, or external command execution. It fits the Read category definition: 'retrieves or queries data; no side effects'. The low severity reflects minimal blast radius if misused by an AI agent—it can only expose form design information without causing data loss, financial impact, or destructive changes.
From the tool's definition Tool name 'readForm' and description 'Read the structure and questions of a Google Form' explicitly indicate retrieval of form metadata without modification.
Attacks that exploit this kind of access
Read the structure and questions of a Google Form. It is categorised as a Read tool in the Google Workspace MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP Server MCP server in PolicyLayer and add a rule for readForm: 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 Workspace MCP Server. Nothing to install.
readForm is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the readForm 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.
Set action: deny in the PolicyLayer policy for readForm. 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.
readForm is provided by the Google Workspace MCP Server MCP server (pm990320/google-workspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →