フォームの回答を取得します
AI agents call get_form_responses to retrieve information from Google Forms 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 or queries form response data from Google Forms—a read operation with no side effects. The blast radius of misuse is minimal; an agent could view responses but cannot modify forms, delete data, execute code, or affect financial operations. Severity is low because form responses are typically non-sensitive metadata and bulk retrieval does not cause system damage.
From the tool's definition Tool name 'get_form_responses' and description (translates to 'Gets form responses') indicate data retrieval without modification. No language suggests alteration, deletion, or execution of arbitrary operations.
Attacks that exploit this kind of access
フォームの回答を取得します. It is categorised as a Read tool in the Google Forms MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Forms MCP Server MCP server in PolicyLayer and add a rule for get_form_responses: 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 Forms MCP Server. Nothing to install.
get_form_responses 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 get_form_responses 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 get_form_responses. 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.
get_form_responses is provided by the Google Forms MCP Server MCP server (masatoshi118/mcp_google_froms). 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 →