find_row_by_unique_id
AI agents call find_row_by_unique_id to retrieve information from Google Connections without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the tool name and context of sibling tools on this Google Sheets-capable server, this appears to be a query operation that retrieves a row by identifier without modifying data. The absence of a description and the read-only nature of the operation place it in the Read category with low severity, as it only queries existing data.
From the tool's definition Tool name 'find_row_by_unique_id' indicates a lookup/query operation with no parameters suggesting modification or deletion. The 'find' verb typically signals retrieval. Description is empty, reducing confidence slightly.
Attacks that exploit this kind of access
find_row_by_unique_id. It is categorised as a Read tool in the Google Connections MCP Server, which means it retrieves data without modifying state.
Register the Google Connections MCP server in PolicyLayer and add a rule for find_row_by_unique_id: 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 Connections. Nothing to install.
find_row_by_unique_id 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 find_row_by_unique_id 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 find_row_by_unique_id. 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.
find_row_by_unique_id is provided by the Google Connections MCP server (michaelzrork/google-connections-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 →