Capture and parse Adobe Analytics and Experience Platform beacons on a webpage
AI agents invoke parse-analytics-beacons to trigger actions in Puppeteer+ MarTech. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool uses Puppeteer (a browser automation framework) to load a webpage and capture live network beacons, which constitutes executing browser actions against an external URL. It doesn't just read static data — it triggers browser-based operations whose effects depend on the target URL argument.
From the tool's definition 'Capture and parse Adobe Analytics and Experience Platform beacons on a webpage' — the tool actively navigates to and interacts with a webpage using Puppeteer to intercept network requests
Documented attack patterns abuse exactly the kind of access parse-analytics-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 parse-analytics-beacons:
{
"version": "1",
"default": "deny",
"tools": {
"parse-analytics-beacons": {
"limits": [
{
"counter": "parse-analytics-beacons_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}parse-analytics-beacons stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Capture and parse Adobe Analytics and Experience Platform beacons on a webpage. It is categorised as a Execute tool in the Puppeteer+ MarTech MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Puppeteer+ MarTech MCP server in PolicyLayer and add a rule for parse-analytics-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.
parse-analytics-beacons is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the parse-analytics-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 parse-analytics-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.
parse-analytics-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.