# get_answering_service_pricing

Get current, human-verified pricing for a specific answering service, virtual receptionist or AI receptionist (e.g. Smith.ai, Ruby, Dialzara, Abby Connect, AnswerConnect). Returns every plan with monthly price, included minutes, setup fees, overage rates, free trial, plus the date the pricing was last verified on the vendor’s own site. Use when someone asks "how much does X cost", "X pricing", "is X worth it", or asks for alternatives to a named service. Covers 21 services, updated weekly.

Agent View of the PolicyLayer registry record for `get_answering_service_pricing`. HTML page: https://policylayer.com/tools/com-fitmycall-pricing/get-answering-service-pricing

## Facts

- Tool: `get_answering_service_pricing`
- Server: FitMyCall — Answering Service Prices (`https://mcp.fitmycall.com/mcp`) — https://policylayer.com/tools/com-fitmycall-pricing.md
- Homepage: https://github.com/https://mcp.fitmycall.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `service` | string | yes | Service name, e.g. "Smith.ai", "Ruby", "Dialzara", "Abby Connect" |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_answering_service_pricing",
    "arguments": {
      "service": "<service>"
    }
  }
}
```

## Why get_answering_service_pricing is rated Low

Even though get_answering_service_pricing only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_answering_service_pricing to retrieve information from FitMyCall — Answering Service Prices 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 FitMyCall — Answering Service Prices:

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

## Other tools on FitMyCall — Answering Service Prices (3)

- `recommend_answering_service_for_industry` — Execute — https://policylayer.com/tools/com-fitmycall-pricing/recommend-answering-service-for-industry.md
- `missed_call_roi` — Read — https://policylayer.com/tools/com-fitmycall-pricing/missed-call-roi.md
- `compare_answering_services` — Write — https://policylayer.com/tools/com-fitmycall-pricing/compare-answering-services.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-fitmycall-pricing · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-fitmycall-pricing