Comprehensive analysis of all marketing and analytics technologies on a webpage
AI agents call scan-marketing-stack to retrieve information from Puppeteer+ MarTech without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool scans and analyzes a webpage to identify marketing and analytics technologies. This is purely an observational/read operation with no side effects, data modification, or destructive actions. It fits the Read category as it queries and retrieves information about existing technologies on a page.
From the tool's definition 'Comprehensive analysis of all marketing and analytics technologies on a webpage' — this is a read/query operation that retrieves and analyzes data from a webpage without modifying anything.
Documented attack patterns abuse exactly the kind of access scan-marketing-stack gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Puppeteer+ MarTech, and nothing reaches the server without passing your rules. This is the rule we recommend for scan-marketing-stack:
{
"version": "1",
"default": "deny",
"tools": {
"scan-marketing-stack": {}
}
} scan-marketing-stack 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.
Comprehensive analysis of all marketing and analytics technologies on a webpage. It is categorised as a Read tool in the Puppeteer+ MarTech MCP Server, which means it retrieves data without modifying state.
Register the Puppeteer+ MarTech MCP server in PolicyLayer and add a rule for scan-marketing-stack: 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 Puppeteer+ MarTech. Nothing to install.
scan-marketing-stack 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-marketing-stack 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-marketing-stack. 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-marketing-stack is provided by the Puppeteer+ MarTech MCP server (moonbirdai/puppeteer-plus-martech-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Puppeteer+ MarTech, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Puppeteer+ MarTech tools catalogued and risk-classified — across an index of 43,000+ MCP servers.