Analyze tag management systems (GTM, Tealium, etc.) on a webpage
AI agents call identify-tag-managers 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.
This tool performs static analysis of a webpage to detect which tag management systems are present. It retrieves and reports information about marketing infrastructure but does not modify content, execute arbitrary code, delete data, or move money.
From the tool's definition Tool name 'identify-tag-managers' and description 'Analyze tag management systems (GTM, Tealium, etc.) on a webpage' indicate passive detection and analysis of existing systems.
Documented attack patterns abuse exactly the kind of access identify-tag-managers 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 identify-tag-managers:
{
"version": "1",
"default": "deny",
"tools": {
"identify-tag-managers": {}
}
}identify-tag-managers 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 tag management systems (GTM, Tealium, etc.) 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 identify-tag-managers: 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.
identify-tag-managers 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 identify-tag-managers 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 identify-tag-managers. 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.
identify-tag-managers 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.