Runlayer Plugin
Unified endpoint
Add one remote MCP endpoint. Users discover and authorize the approved tools available to them without accumulating separate client configurations.
Runlayer for Perplexity
Bring approved MCP tools into Perplexity through Runlayer’s remote endpoints.
01
Connect
Give everyone in Perplexity the golden path to approved tools
Add one Runlayer Plugin endpoint so people find every tool they’re approved for, or connect a single server when you want a narrower set.
Direct connection
Per-connector endpoint
Give the client a dedicated Runlayer URL for one connector. Identity, policy, scanning, and audit still stay attached to every request.
Connection support
Remote MCP
02
Observe
See how Perplexity is being used
Runlayer uses every channel Perplexity exposes. Each one is labeled, so you can tell real-time hooks from after-the-fact imports.
Managed browser extension
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Read the guide03
Enforce
Know exactly what Perplexity can block
Each row reflects Runlayer’s enforcement code for Perplexity: what it can stop before a call runs, block afterward, or redact in place.
| Control | Support | What that means |
|---|---|---|
| Pre-tool deny | At the gateway | Runlayer has no hook in Perplexity that can stop a tool call; Runlayer policies stop calls to Runlayer connectors at the gateway. |
| Post-tool output block | At the gateway | Runlayer has no hook in Perplexity that can block tool output; ToolGuard blocks unsafe output from Runlayer connectors at the gateway. |
| Output rewrite | At the gateway | Runlayer has no hook in Perplexity that can rewrite tool output; ToolGuard masks sensitive output from Runlayer connectors at the gateway. |
Enforcement postureNot applicable
Minimum supported versionNo minimum listed
MCP servers
Connect Perplexity to the tools your teams use
Setup steps, tools, and controls for each MCP server in Perplexity.
