AI agents invoke perplexity_login to trigger actions in PPX-MCP. 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.
This tool launches a browser, automates the login process, and extracts/saves authentication cookies — it triggers external browser operations and persists sensitive credential data (cookies), making it an Execute action with high severity due to the risk of credential theft or session hijacking if misused.
From the tool's definition 'Opens a browser window to log in to Perplexity and automatically saves cookies' and 'cookies are extracted and saved'
Attacks that exploit this kind of access
Opens a browser window to log in to Perplexity and automatically saves cookies. User must complete login in the browser, then the cookies are extracted and saved. It is categorised as a Execute tool in the PPX-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PPX- MCP server in PolicyLayer and add a rule for perplexity_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 PPX-MCP. Nothing to install.
perplexity_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 perplexity_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 perplexity_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.
perplexity_login is provided by the PPX- MCP server (mahii1972/ppx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →