# Perplexity — Tool approvals for MCP and connector calls

- Company: Perplexity (perplexity.ai)
- Announced: 2026-10-19T17:21:52+00:00
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://docs.perplexity.ai/docs/resources/changelog#october-2026
- Record: https://forck.live/items/24670-tool-approvals-for-mcp-and-connector-calls
- Subject: Sonar

Perplexity added an optional approval step that lets developers review MCP and connector tool calls before they run. Setting `require_approval` on an MCP or connector tool makes a call stop and return an `mcp_approval_request` item instead of executing. Developers approve or deny that request by sending an `mcp_approval_response` with `previous_response_id`. The setting accepts `"always"` to review every call, or a filter object that skips approval for selected tools or for read-only tools. Calls still run without approval by default, so the behaviour applies only where the setting is used. The Python SDK 0.43.8 and TypeScript SDK 0.38.8 include the approval types.

## Evidence

Verbatim from https://docs.perplexity.ai/docs/resources/changelog#october-2026:

> Set
> require_approval
> on an
> mcp
> or
> connector
>  tool to review calls before they run. A call that needs approval returns an
> mcp_approval_request
>  item and does not run.

---

Record: https://forck.live/items/24670-tool-approvals-for-mcp-and-connector-calls
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md