get_contact_summary
Rolodex overview: how many contacts the subscriber has, how many have a phone or email, and the top industries and tags. Answers "how many contacts do I have?" and "what industries are my contacts in?" Use get_contact_history to look up specific people.
This record as markdown: /tools/com-getsavitools-savi-tools/get-contact-summary.md
What get_contact_summary does on Savi Tools
AI agents call get_contact_summary 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.
Why get_contact_summary is rated Low
This tool retrieves and queries existing contact data in aggregate form only. There are no side effects, no data creation or modification, no code execution, and no financial operations. It is a straightforward read operation that returns statistical summaries of the user's contact database.
From the tool's definition Tool provides aggregate overview statistics: 'how many contacts the subscriber has, how many have a phone or email, and the top industries and tags.' It retrieves summary data without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
The rule that runs get_contact_summary 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_summary, this is the rule to start with:
get_contact_summary 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_summary call is checked against it from then on.
Questions about get_contact_summary
Rolodex overview: how many contacts the subscriber has, how many have a phone or email, and the top industries and tags. Answers "how many contacts do I have?" and "what industries are my contacts in?" Use get_contact_history to look up specific people. It is categorised as a Read tool in the Savi Tools MCP Server, which means it retrieves data without modifying state.
Register the Savi Tools MCP server in PolicyLayer and add a rule for get_contact_summary: 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_summary 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_summary 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_summary. 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_summary 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