Fetch a landing page over HTTP(S) and extract structured
AI agents call google_ads_landing_page_analyze to retrieve information from Mureo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and analyzes landing page content, which is a read operation. However, it performs HTTP(S) requests to arbitrary external URLs, creating moderate risk: (1) server-side request forgery (SSRF) if URLs are attacker-controlled, (2) exposure of internal network topology if targeting internal endpoints, (3) potential for data exfiltration if landing pages contain sensitive information.
From the tool's definition Tool name contains 'analyze' and description states 'Fetch a landing page over HTTP(S) and extract structured' — indicates retrieval and analysis of external content with no modification.
Documented attack patterns abuse exactly the kind of access google_ads_landing_page_analyze gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for google_ads_landing_page_analyze:
{
"version": "1",
"default": "deny",
"tools": {
"google_ads_landing_page_analyze": {}
}
}google_ads_landing_page_analyze 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.
Fetch a landing page over HTTP(S) and extract structured. It is categorised as a Read tool in the Mureo MCP Server, which means it retrieves data without modifying state.
Register the Mureo MCP server in PolicyLayer and add a rule for google_ads_landing_page_analyze: 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 Mureo. Nothing to install.
google_ads_landing_page_analyze 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 google_ads_landing_page_analyze 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 google_ads_landing_page_analyze. 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.
google_ads_landing_page_analyze is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, 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.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.