historical_analysis
AI agents call historical_analysis to retrieve information from Pornhub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve or query historical data about trends, performers, or platform analytics based on the server's purpose and sibling tool patterns. However, the empty description significantly limits confidence in this classification. No evidence suggests data modification, deletion, or external execution.
From the tool's definition Tool named 'historical_analysis' with empty description; sibling tools perform 'analyze', 'compare', and 'search' operations on adult entertainment industry data. Historical analysis implies querying and retrieving historical data without modification.
Attacks that exploit this kind of access
historical_analysis. It is categorised as a Read tool in the Pornhub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pornhub MCP Server MCP server in PolicyLayer and add a rule for historical_analysis: 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 Pornhub MCP Server. Nothing to install.
historical_analysis 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 historical_analysis 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 historical_analysis. 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.
historical_analysis is provided by the Pornhub MCP Server MCP server (talhelf/ph-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 →