Analyze network requests for tracking and marketing activities
AI agents call track-marketing-beacons 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 analyzes (reads) network requests to identify tracking and marketing beacons. It does not create, modify, delete, or execute anything; it is purely observational. Severity is medium because it could expose sensitive network traffic details including user tracking data and third-party integrations, which could be misused for competitive intelligence or privacy analysis.
From the tool's definition "Analyze network requests for tracking and marketing activities" — the tool reads/inspects network traffic
Documented attack patterns abuse exactly the kind of access track-marketing-beacons 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 track-marketing-beacons:
{
"version": "1",
"default": "deny",
"tools": {
"track-marketing-beacons": {}
}
}track-marketing-beacons 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.
Analyze network requests for tracking and marketing activities. 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 track-marketing-beacons: 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.
track-marketing-beacons 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 track-marketing-beacons 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 track-marketing-beacons. 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.
track-marketing-beacons 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.