AI agents call search_google_ads to retrieve information from LeadMagic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves advertising campaign information through the LeadMagic API. The verb 'search' and the read-only nature of querying ad data (no side effects, no modifications, no code execution) places it clearly in the Read category. The severity is low because it only accesses publicly or semi-publicly available advertising intelligence data with no destructive or operational consequences.
From the tool's definition Tool name 'search_google_ads' and description 'Search for Google Ads based on company' indicate a search/query operation with no modification or execution of external systems.
Documented attack patterns abuse exactly the kind of access search_google_ads gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LeadMagic MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_google_ads:
{
"version": "1",
"default": "deny",
"tools": {
"search_google_ads": {}
}
}search_google_ads 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.
Search for Google Ads based on company\. It is categorised as a Read tool in the LeadMagic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the LeadMagic MCP Server MCP server in PolicyLayer and add a rule for search_google_ads: 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 LeadMagic MCP Server. Nothing to install.
search_google_ads 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 search_google_ads 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 search_google_ads. 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.
search_google_ads is provided by the LeadMagic MCP Server MCP server (leadmagic/leadmagic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LeadMagic MCP Server, 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.
19 LeadMagic MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.