AI agents use save_monitor_notifications 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 |
|---|---|---|---|
daily_report | number | Yes | Daily report: 1=Enabled, 0=Disabled |
weekly_report | number | Yes | Weekly report: 1=Enabled, 0=Disabled |
notification_email | string | Yes | Notification email address |
notification_status | number | Yes | Notification status: 1=Enabled, 0=Disabled |
instant_ad_notification | number | Yes | Instant ad notification: 1=Enabled, 0=Disabled |
instant_product_notification | number | Yes | Instant product notification: 1=Enabled, 0=Disabled |
Parameters from the server's own tool schema.
This tool modifies user-facing settings for notification delivery and reporting, which classifies it as Write rather than Read (it changes state). It is not Destructive because notification settings can be updated or reverted.
From the tool's definition The tool description states 'Save notification settings (email, instant alerts, reports)' — this indicates it creates or modifies configuration data (notification preferences) that can be reversed or updated later.
Attacks that exploit this kind of access
Save notification settings (email, instant alerts, reports). 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.
save_monitor_notifications accepts 6 parameters: daily_report, weekly_report, notification_email, notification_status, instant_ad_notification, instant_product_notification. Required: daily_report, weekly_report, notification_email, notification_status, instant_ad_notification, instant_product_notification. 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 save_monitor_notifications: 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.
save_monitor_notifications 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 save_monitor_notifications 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 save_monitor_notifications. 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.
save_monitor_notifications 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 →