Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Retu...
Part of the Activecampaign server.
Free to start. No card required.
AI agents call scan_competitor_ai_presence to retrieve information from Activecampaign 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 scan_competitor_ai_presence 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": {
"scan_competitor_ai_presence": {}
}
}See the full Activecampaign policy for all 26 tools.
These attack patterns abuse exactly the kind of access scan_competitor_ai_presence 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.
Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.. It is categorised as a Read tool in the Activecampaign MCP Server, which means it retrieves data without modifying state.
Register the Activecampaign MCP server in PolicyLayer and add a rule for scan_competitor_ai_presence: 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 Activecampaign. Nothing to install.
scan_competitor_ai_presence 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 scan_competitor_ai_presence 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 scan_competitor_ai_presence. 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.
scan_competitor_ai_presence is provided by the Activecampaign MCP server (https://gateway.pipeworx.io/activecampaign/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Activecampaign 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.