AI agents use create_monitor_task to create or update resources in Pipiads — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pipiads environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
advertiser_id | string | Yes | Facebook advertiser ID from search results |
advertiser_name | string | — | Advertiser name |
monitor_task_type | number | — | Monitor task type |
Parameters from the server's own tool schema.
The tool creates a new resource (a monitoring task) which is a reversible write operation. While it doesn't retrieve data (Read) or execute arbitrary code (Execute), it does establish persistent state in the advertising intelligence platform. Severity is medium because misuse could result in unwanted monitoring of competitors' ads or resource consumption, but the operation itself is not destructive or financial.
From the tool's definition Tool name includes 'create' and description states 'Create an ad monitoring task' — this is a creation operation that modifies state by adding a new monitoring task to the PipiAds system.
Attacks that exploit this kind of access
Create an ad monitoring task for a Facebook advertiser. It is categorised as a Write tool in the Pipiads MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_monitor_task accepts 3 parameters: advertiser_id, advertiser_name, monitor_task_type. Required: advertiser_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 create_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.
create_monitor_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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 →