# 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.

Agent View of the PolicyLayer registry record for `get_contact_summary`. HTML page: https://policylayer.com/tools/com-getsavitools-savi-tools/get-contact-summary

## Facts

- Tool: `get_contact_summary`
- Server: Savi Tools (`https://getsavitools.com/api/mcp`) — https://policylayer.com/tools/com-getsavitools-savi-tools.md
- Homepage: https://github.com/https://getsavitools.com/api/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_contact_summary",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Savi Tools:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_contact_summary": {}
  }
}
```

## Other tools on Savi Tools (24)

- `get_1099_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-1099-summary.md
- `get_business_profile` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-business-profile.md
- `get_business_snapshot` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-business-snapshot.md
- `get_cash_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-cash-summary.md
- `get_client_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-client-summary.md
- `get_contact_history` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-contact-history.md
- `get_cost_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-cost-summary.md
- `get_expense_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-expense-summary.md
- `get_goals_progress` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-goals-progress.md
- `get_invoice_details` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-invoice-details.md
- `get_mileage_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-mileage-summary.md
- `get_profitability` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-profitability.md
- `get_project_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-project-summary.md
- `get_revenue_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-revenue-summary.md
- `get_tax_deductions` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-tax-deductions.md
- `get_tax_setaside` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-tax-setaside.md
- `get_time_summary` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/get-time-summary.md
- `list_bills_owed` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-bills-owed.md
- `list_clients` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-clients.md
- `list_outstanding_invoices` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-outstanding-invoices.md
- `list_projects` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-projects.md
- `list_recent_expenses` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-recent-expenses.md
- `list_recent_invoices` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-recent-invoices.md
- `list_uncategorized_transactions` — Read — https://policylayer.com/tools/com-getsavitools-savi-tools/list-uncategorized-transactions.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-getsavitools-savi-tools · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-getsavitools-savi-tools