AI agents call get_monitor_longest_run_copy 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 |
|---|---|---|---|
page | number | — | Page number |
task_id | string | Yes | Monitor task ID |
order_by | string | — | Sort field |
per_page | number | — | Results per page |
direction | string | — | "asc" or "desc" |
Parameters from the server's own tool schema.
This tool retrieves or queries existing data about ad copy performance in a monitoring context. The verb 'get' and the absence of any modification language (create, update, delete, execute) clearly indicate a read-only operation. No side effects, data modification, or external operations are implied.
From the tool's definition Tool name 'get_monitor_longest_run_copy' and description 'Get longest-running ad copy for a monitor task' indicate a retrieval operation that queries monitoring data without modification.
Attacks that exploit this kind of access
Get longest-running ad copy for a monitor task. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
get_monitor_longest_run_copy accepts 5 parameters: page, task_id, order_by, per_page, direction. Required: task_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_monitor_longest_run_copy: 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_monitor_longest_run_copy 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_monitor_longest_run_copy 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_monitor_longest_run_copy. 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_monitor_longest_run_copy 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 →