AI agents call search_lib_ads to retrieve information from Pipiads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number |
country | string | — | Country filter |
language | string | — | Language filter |
order_by | string | — | Sort field |
per_page | integer | — | Results per page |
ad_status | string | — | Ad status filter |
data_type | string | — | Data type filter |
direction | string | — | "asc" or "desc" |
ad_content | string | — | Ad content keyword search |
ad_cost_end | number | — | Maximum ad cost |
ad_forecast | number | — | Ad forecast filter |
ad_platform | string | — | Ad platform filter |
Parameters from the server's own tool schema.
This tool performs a read-only search against Meta's Ad Library, applying various filters to retrieve existing advertisement data. There are no side effects, data modifications, deletions, code execution, or financial transactions involved. The operation is purely informational retrieval, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'search_lib_ads' and description 'Search Meta Ad Library ads. Filter by content, platform, status, cost, reach, active days.' indicate a search/query operation that retrieves advertising data without modifying or deleting anything.
Risk signalsHigh parameter count (28 properties)
Attacks that exploit this kind of access
Search Meta Ad Library ads. Filter by content, platform, status, cost, reach, active days. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
search_lib_ads accepts 12 parameters: page, country, language, order_by, per_page, ad_status, data_type, direction, ad_content, ad_cost_end, ad_forecast, ad_platform. The full parameter table on this page comes from the server's own tool schema.
Register the Pipiads MCP server in PolicyLayer and add a rule for search_lib_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 Pipiads. Nothing to install.
search_lib_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_lib_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_lib_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_lib_ads is provided by the Pipiads MCP server (pipiads-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →