AI agents call get_store_fb_pages 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 |
|---|---|---|---|
id | string | Yes | Store ID |
page_size | number | — | Results per page |
current_page | number | — | Page number |
Parameters from the server's own tool schema.
This tool retrieves publicly available advertiser page information from Meta Ad Library. It performs a straightforward read operation that queries existing data without creating, modifying, deleting, executing code, or initiating financial transactions. The blast radius is minimal—an agent misusing this tool could only retrieve information already publicly accessible through Meta's Ad Library interface.
From the tool's definition Tool description states 'Get store Facebook advertiser pages' — a retrieval operation with no modification capability. The verb 'Get' indicates data querying with no side effects.
Attacks that exploit this kind of access
Get store Facebook advertiser pages from Meta Ad Library. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_fb_pages accepts 3 parameters: id, page_size, current_page. Required: id. 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 get_store_fb_pages: 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.
get_store_fb_pages 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 get_store_fb_pages 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 get_store_fb_pages. 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.
get_store_fb_pages 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 →