Cancel an ad monitoring task.
AI agents call cancel_monitor_task to permanently remove resources in Pipiads — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
task_id | string | Yes | Monitor task ID to cancel |
Parameters from the server's own tool schema.
Cancelling a monitoring task is typically irreversible - once cancelled, the task's ongoing monitoring state, collected data, and scheduling are lost. This falls under Destructive as the action cannot be undone. Severity is medium as it affects monitoring operations but does not delete financial data or core system components.
From the tool's definition 'Cancel an ad monitoring task' - cancelling a task is an irreversible action that stops and removes an active monitoring task
Attacks that exploit this kind of access
Cancel an ad monitoring task. It is categorised as a Destructive tool in the Pipiads MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_monitor_task accepts 1 parameter: task_id. 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 cancel_monitor_task: 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.
cancel_monitor_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_monitor_task 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 cancel_monitor_task. 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.
cancel_monitor_task 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 →