AI agents call get_store_ad_copy_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 |
sort_key | string | — | Sort field |
page_size | number | — | Results per page |
sort_type | string | — | "asc" or "desc" |
current_page | number | — | Page number |
Parameters from the server's own tool schema.
This tool retrieves advertising intelligence data (ad copy analysis) for analytical purposes. It has no side effects—it does not create, modify, delete, or execute operations. The 'get' operation is explicitly read-only, and the sibling tools on this server (which include ai_search_* and submit operations) confirm this is part of a query-focused advertising intelligence platform.
From the tool's definition Tool name and description indicate it 'Get[s]' store TikTok ad copy analysis with pagination. The verb 'get' and lack of any modifying language (create, update, delete) indicate pure data retrieval.
Attacks that exploit this kind of access
Get store TikTok ad copy analysis with pagination. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_ad_copy_analysis accepts 5 parameters: id, sort_key, page_size, sort_type, 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_ad_copy_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_ad_copy_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_ad_copy_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_ad_copy_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_ad_copy_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 →