search_linkedin_ad_library
Search the ads running on LinkedIn, from LinkedIn\u2019s OWN Ad Library, and get three things no ad scrape can give you: the advertiser\u2019s actual TARGETING (location, language, audience, company, job, age, gender, interests, traits \u2014 both the segments they INCLUDED and the ones they EXCL...
This record as markdown: /tools/hermoso/search-linkedin-ad-library.md
What search_linkedin_ad_library does on Hermoso
AI agents call search_linkedin_ad_library to retrieve information from Hermoso without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_linkedin_ad_library is rated Low
Even though search_linkedin_ad_library only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_linkedin_ad_library safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_linkedin_ad_library, this is the rule to start with:
search_linkedin_ad_library is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every search_linkedin_ad_library call is checked against it from then on.
Questions about search_linkedin_ad_library
Search the ads running on LinkedIn, from LinkedIn\u2019s OWN Ad Library, and get three things no ad scrape can give you: the advertiser\u2019s actual TARGETING (location, language, audience, company, job, age, gender, interests, traits \u2014 both the segments they INCLUDED and the ones they EXCLUDED), estimated impressions as a range plus the percentage split BY COUNTRY, and, for ads LinkedIn REMOVED, the advertising policy that was violated and how it was caught. That last one is the cheapest way to learn what not to write. It is GLOBAL, not an EU-only transparency feed. COVERAGE IS BOUNDED and the reply always says so: nothing created before 2023-06-01, and an ad is dropped one year after its last impression, so an empty result usually means the window rather than the market. 25 ads per page. Needs LinkedIn connected \u2014 no extra permission, any LinkedIn connection works. 0 credits. It is categorised as a Read tool in the Hermoso MCP Server, which means it retrieves data without modifying state.
Register the Hermoso MCP server in PolicyLayer and add a rule for search_linkedin_ad_library: 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 Hermoso. Nothing to install.
search_linkedin_ad_library 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_linkedin_ad_library 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_linkedin_ad_library. 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_linkedin_ad_library is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
This server
Across the catalogue