AI agents call get_store_delivery_analysis 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 |
Parameters from the server's own tool schema.
This tool retrieves and queries advertising delivery analytics from Meta's Ad Library. It performs a read-only operation returning intelligence/analysis data about ad performance and delivery metrics. There are no side effects, no data modification, no code execution, and no financial implications. This is a straightforward data retrieval use case typical of advertising intelligence APIs.
From the tool's definition Tool name and description indicate retrieval of advertising analytics: 'Get store Meta Ad Library in-depth delivery analysis.' The verb 'Get' combined with 'analysis' suggests querying and retrieving existing data from an ad library, with no modification,…
Attacks that exploit this kind of access
Get store Meta Ad Library in-depth delivery analysis. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_delivery_analysis accepts 1 parameter: id. 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_delivery_analysis: 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_delivery_analysis 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_delivery_analysis 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_delivery_analysis. 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_delivery_analysis 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 →