remove_link_by_search
AI agents call remove_link_by_search to permanently remove resources in Google Connections — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'remove_link_by_search' implies irreversible removal of link(s) found by a search query. 'Remove' typically implies deletion, which could affect multiple items if the search matches broadly. The empty description lowers confidence, but the 'remove' verb and the context of a server with CRUD operations on Google Workspace services suggests a Destructive action.
From the tool's definition Tool name 'remove_link_by_search' suggests deletion/removal of links based on search criteria; description is empty and uninformative.
Attacks that exploit this kind of access
remove_link_by_search. It is categorised as a Destructive tool in the Google Connections MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Google Connections MCP server in PolicyLayer and add a rule for remove_link_by_search: 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.
remove_link_by_search is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_link_by_search 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 remove_link_by_search. 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.
remove_link_by_search 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 →