Get responses submitted to a Google Form.
AI agents call getFormResponses 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 retrieves form response data without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The only risk is potential information disclosure if sensitive form responses are exposed, but this is typical for read operations and would depend on access controls rather than the tool's inherent capability.
From the tool's definition Tool name 'getFormResponses' and description 'Get responses submitted to a Google Form' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get responses submitted to 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 getFormResponses: 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.
getFormResponses 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 getFormResponses 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 getFormResponses. 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.
getFormResponses 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 →