AI agents call get_store_ad_schedule 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 |
type | number | — | Data type |
time_end | number | — | End time (unix timestamp) |
time_start | number | — | Start time (unix timestamp) |
Parameters from the server's own tool schema.
This tool retrieves or queries ad campaign schedule information from a store without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with no side effects, making it the lowest risk category.
From the tool's definition Tool name 'get_store_ad_schedule' and description 'Get store ad campaign schedule' both indicate a retrieval operation with the verb 'Get', which queries existing ad schedule data without modification.
Attacks that exploit this kind of access
Get store ad campaign schedule. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_store_ad_schedule accepts 4 parameters: id, type, time_end, time_start. 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_schedule: 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_schedule 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_schedule 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_schedule. 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_schedule 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 →