get_contact_history
Search the subscriber’s own contacts by name, company, industry, or profession. Returns each match with phone/mobile/email, title, company, industry, tags, and relationship history. Answers "I am about to call the Chens, what is our history?" and "list my real-estate contacts with their phone num...
This record as markdown: /tools/com-getsavitools-savi-tools/get-contact-history.md
What get_contact_history does on Savi Tools
AI agents call get_contact_history to retrieve information from Savi Tools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | Yes | Name or company to search for. |
Parameters from the server's own tool schema.
Why get_contact_history is rated Low
This tool retrieves and queries contact information from the subscriber's own database. It performs a lookup operation that has no side effects—it neither creates, modifies, deletes, nor executes external operations. The data returned is read-only information about existing contacts. The inclusion of a 'doNotShare' flag is a display/filter concern, not a side effect. This is a classic Read category tool.
From the tool's definition Tool description explicitly states it 'Search[es] the subscriber's own contacts' and 'Returns each match with phone/mobile/email, title, company, industry, tags, and relationship history.' The verb 'search' and 'returns' indicate data retrieval with no…
Attacks that exploit this kind of access
The rule that runs get_contact_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Savi Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_contact_history, this is the rule to start with:
get_contact_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Savi Tools, apply this rule, and every get_contact_history call is checked against it from then on.
Questions about get_contact_history
Search the subscriber’s own contacts by name, company, industry, or profession. Returns each match with phone/mobile/email, title, company, industry, tags, and relationship history. Answers "I am about to call the Chens, what is our history?" and "list my real-estate contacts with their phone numbers." Contacts flagged doNotShare asked not to be passed along. It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
get_contact_history accepts 1 parameter: query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Savi Tools MCP server in PolicyLayer and add a rule for get_contact_history: 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 Savi Tools. Nothing to install.
get_contact_history 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_history 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_history. 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_history is provided by the Savi Tools MCP server (https://getsavitools.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Savi Tools, and thousands of servers like it.
This server
Across the catalogue