Analyze meta tags, titles, and descriptions on a webpage
AI agents call check-page-metadata 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 passive analysis of webpage metadata (meta tags, titles, descriptions). It retrieves and inspects data without creating, modifying, deleting, or executing code. The sibling tools (analyze-analytics-platforms, audit-seo, detect-ad-pixels, etc.) are similarly read-only analysis functions. No side effects or state changes occur.
From the tool's definition Tool description states it 'Analyze[s] meta tags, titles, and descriptions on a webpage' — purely retrieval and inspection of existing metadata with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access check-page-metadata 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 check-page-metadata:
{
"version": "1",
"default": "deny",
"tools": {
"check-page-metadata": {}
}
}check-page-metadata 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 meta tags, titles, and descriptions 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 check-page-metadata: 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.
check-page-metadata 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 check-page-metadata 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 check-page-metadata. 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.
check-page-metadata 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.