Check if code or dependencies might be using deprecated features
AI agents call check_deprecated_code to retrieve information from Perplexity AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or analyzes code to identify deprecated patterns and dependencies. It retrieves information about code quality/compliance but does not create, modify, delete, or execute arbitrary operations. It is purely informational, matching the 'Read' category.
From the tool's definition Tool name 'check_deprecated_code' and description 'Check if code or dependencies might be using deprecated features' indicate analysis and inspection of existing code without modification.
Attacks that exploit this kind of access
Check if code or dependencies might be using deprecated features. It is categorised as a Read tool in the Perplexity AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Perplexity AI 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 AI 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 AI MCP Server MCP server (rileyedwards77/perplexity-mcp-server). 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 →