set_notification_preference
Update a single notification preference toggle. Valid keys: booking_reminders, payment_reminders, quote_reminders, quote_followup, contract_reminders, proposal_reminders, delivery_reminders, gallery_reminders.
This record as markdown: /tools/app-businys-mcp-server/set-notification-preference.md
What set_notification_preference does on Businys
AI agents use set_notification_preference to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.
Why set_notification_preference is rated Medium
This tool creates or modifies data reversibly by toggling notification preferences. It does not read data without side effects (Read), execute arbitrary operations (Execute), delete data (Destructive), or involve financial transactions (Financial). The blast radius is minimal: a user can easily toggle preferences back.
From the tool's definition Tool description explicitly states 'Update a single notification preference toggle' — a modification operation on user settings.
Attacks that exploit this kind of access
The rule that runs set_notification_preference safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_notification_preference, this is the rule to start with:
set_notification_preference stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every set_notification_preference call is checked against it from then on.
Questions about set_notification_preference
Update a single notification preference toggle. Valid keys: booking_reminders, payment_reminders, quote_reminders, quote_followup, contract_reminders, proposal_reminders, delivery_reminders, gallery_reminders. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Businys MCP server in PolicyLayer and add a rule for set_notification_preference: 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 Businys. Nothing to install.
set_notification_preference 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 set_notification_preference 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 set_notification_preference. 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.
set_notification_preference is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Businys, and thousands of servers like it.
This server
Across the catalogue