Automatically call this tool when working with unfamiliar APIs/libraries, needing usage examples, or checking version specifics as this can access web. Example: When adding a payment gateway, ask
AI agents call get_documentation to retrieve information from Perplexity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only documentation lookup and web retrieval without side effects. It queries information about APIs and libraries but does not execute code, modify data, delete resources, or commit financial transactions. The 'Example' mentioning 'payment gateway' refers only to documentation retrieval context, not actual payment processing.
From the tool's definition Tool description states it 'access[es] web' to retrieve 'usage examples' and 'version specifics' for documentation lookup. The action is retrieval-only with no modification, deletion, or code execution capability.
Documented attack patterns abuse exactly the kind of access get_documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Perplexity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_documentation": {}
}
}get_documentation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Automatically call this tool when working with unfamiliar APIs/libraries, needing usage examples, or checking version specifics as this can access web. Example: When adding a payment gateway, ask. It is categorised as a Read tool in the Perplexity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexity MCP Server MCP server in PolicyLayer and add a rule for get_documentation: 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 MCP Server. Nothing to install.
get_documentation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_documentation 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 get_documentation. 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.
get_documentation is provided by the Perplexity MCP Server MCP server (wysh3/perplexity-mcp-zerver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Perplexity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Perplexity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.