AI agents call get_contact to retrieve information from MCP Google Contacts Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves contact information by identifier without any side effects. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The use of 'get' verb and the retrieval-only nature of the operation confirm low severity, as misuse would only expose existing contact data rather than modify, delete, or create unauthorized access to systems.
From the tool's definition Tool name 'get_contact' and description 'Get a contact by resource name or email' indicate a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access get_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Google Contacts Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_contact:
{
"version": "1",
"default": "deny",
"tools": {
"get_contact": {}
}
}get_contact is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get a contact by resource name or email. It is categorised as a Read tool in the MCP Google Contacts Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Contacts Server MCP server in PolicyLayer and add a rule for get_contact: 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 MCP Google Contacts Server. Nothing to install.
get_contact 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_contact 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_contact. 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_contact is provided by the MCP Google Contacts Server MCP server (rayanzaki/mcp-google-contacts-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 MCP Google Contacts Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
9 MCP Google Contacts Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.