AI agents invoke ask_perplexity to trigger actions in Proxima. 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.
Based on sibling tools (ask_chatgpt, ask_claude, ask_gemini) and the server description, this tool likely sends a query to the Perplexity AI provider and returns a response, triggering an external API call. This constitutes an Execute-level action (triggering external operations). Confidence is lowered due to empty description.
From the tool's definition Tool name 'ask_perplexity' and server context describing connections to multiple AI providers including Perplexity; description is empty/uninformative.
Documented attack patterns abuse exactly the kind of access ask_perplexity gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for ask_perplexity:
{
"version": "1",
"default": "deny",
"tools": {
"ask_perplexity": {
"limits": [
{
"counter": "ask_perplexity_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ask_perplexity 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.
ask_perplexity. It is categorised as a Execute tool in the Proxima MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxima MCP server in PolicyLayer and add a rule for ask_perplexity: 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 Proxima. Nothing to install.
ask_perplexity 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 ask_perplexity 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 ask_perplexity. 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.
ask_perplexity is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.