AI agents call get_store_ad_trend 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 |
end_time | number | Yes | End time (unix timestamp) |
start_time | number | Yes | Start time (unix timestamp) |
Parameters from the server's own tool schema.
This tool retrieves and queries ad trend data from Meta Ad Library based on time parameters. It is a read-only operation that fetches analytics/intelligence data without modifying, executing code, deleting, or committing financial transactions. The low severity reflects minimal risk from misuse—an AI agent querying ad trends presents no significant blast radius.
From the tool's definition Tool description states 'Get store Meta Ad Library ad trend analysis' with required parameters start_time and end_time. The verb 'Get' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Get store Meta Ad Library ad trend analysis. Requires start_time and end_time. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_ad_trend accepts 3 parameters: id, end_time, start_time. Required: id, end_time, start_time. 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_ad_trend: 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_ad_trend 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_ad_trend 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_ad_trend. 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_ad_trend 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 →