Submit a competitor analysis job. Analyzes a competitor's website across 15+ data sources (SEO, traffic, social, Product Hunt, GitHub, Wayback Machine history, AI-generated insights, etc.) and returns a job_id. Use get_report_status(job_id) to poll and get_report(job_id) to retrieve results when ...
Risk signalsAccepts URL/endpoint input (url)
Part of the Analook — Competitor Intelligence server.
Free to start. No card required.
AI agents call analyze_competitor to retrieve information from Analook — Competitor Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though analyze_competitor only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"analyze_competitor": {}
}
}See the full Analook — Competitor Intelligence policy for all 5 tools.
These attack patterns abuse exactly the kind of access analyze_competitor gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Submit a competitor analysis job. Analyzes a competitor's website across 15+ data sources (SEO, traffic, social, Product Hunt, GitHub, Wayback Machine history, AI-generated insights, etc.) and returns a job_id. Use get_report_status(job_id) to poll and get_report(job_id) to retrieve results when status='completed'. Typical analysis takes 2-5 minutes. Requires authentication (deducts 1 credit from your Analook balance). Args: url: Competitor website URL (e.g. 'https://linear.app' or 'lovable.dev') product_name: Optional product name override (defaults to domain) Returns: {job_id: str, status: 'started', poll_url: str} on success {error: str, hint?: str} on auth/validation failure. It is categorised as a Read tool in the Analook — Competitor Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Analook — Competitor Intelligence MCP server in PolicyLayer and add a rule for analyze_competitor: 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 Analook — Competitor Intelligence. Nothing to install.
analyze_competitor 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 analyze_competitor 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 analyze_competitor. 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.
analyze_competitor is provided by the Analook — Competitor Intelligence MCP server (https://www.analook.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Analook — Competitor Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.