Automatically call this tool when reviewing legacy code, planning upgrades, or encountering warnings with real time web access. Helps identify technical debt. Example: During code reviews or before upgrading dependencies.
AI agents call check_deprecated_code 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's primary function is to query and retrieve information about deprecated code patterns and technical debt. It uses web access to gather data for analysis purposes but does not execute code, make modifications, or cause destructive changes. The use case (code reviews, dependency upgrade planning) confirms it is informational and read-only.
From the tool's definition The tool 'check_deprecated_code' is described as helping to 'identify technical debt' during 'code reviews or before upgrading dependencies.' It performs analysis and review activities with 'real time web access' but does not modify, delete, or execute…
Documented attack patterns abuse exactly the kind of access check_deprecated_code 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 check_deprecated_code:
{
"version": "1",
"default": "deny",
"tools": {
"check_deprecated_code": {}
}
}check_deprecated_code 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 reviewing legacy code, planning upgrades, or encountering warnings with real time web access. Helps identify technical debt. Example: During code reviews or before upgrading dependencies. 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 check_deprecated_code: 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.
check_deprecated_code 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 check_deprecated_code 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 check_deprecated_code. 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.
check_deprecated_code 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.