Check if you are authenticated on Perplexity.ai. If not, opens a browser window so you can log in.
AI agents invoke login to trigger actions in Perplexity Web. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool performs browser automation (opening a browser window) which is an external operation triggered by the tool. While its primary purpose is authentication checking, it actively launches a browser when unauthenticated, making it an Execute-category tool. Misuse could open unwanted browser sessions or be used to initiate phishing-style interactions.
From the tool's definition 'opens a browser window so you can log in' — triggers external browser automation operation
Documented attack patterns abuse exactly the kind of access login gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Perplexity Web, and nothing reaches the server without passing your rules. This is the rule we recommend for login:
{
"version": "1",
"default": "deny",
"tools": {
"login": {
"limits": [
{
"counter": "login_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}login stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if you are authenticated on Perplexity.ai. If not, opens a browser window so you can log in. It is categorised as a Execute tool in the Perplexity Web MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Perplexity Web MCP server in PolicyLayer and add a rule for login: 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 Perplexity Web. Nothing to install.
login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the login 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 login. 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.
login is provided by the Perplexity Web MCP server (quequiere/perplexity-web-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Perplexity Web, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Perplexity Web tools catalogued and risk-classified — across an index of 43,000+ MCP servers.