get_notification_preferences
Get current notification preference toggles (booking reminders, payment reminders, quote follow-ups, etc.).
This record as markdown: /tools/app-businys-mcp-server/get-notification-preferences.md
What get_notification_preferences does on Businys
AI agents call get_notification_preferences to retrieve information from Businys without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_notification_preferences is rated Low
This tool retrieves user notification preference settings without modifying, executing, or deleting anything. It is a straightforward query operation that returns configuration data. The blast radius of misuse is minimal – an attacker could only view notification preferences, not change them or access sensitive business data like financial records or client details.
From the tool's definition Tool description states "Get current notification preference toggles" – the verb "Get" and the focus on retrieving current state indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_notification_preferences 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 get_notification_preferences, this is the rule to start with:
get_notification_preferences is read-only, so it stays allowed. 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 get_notification_preferences call is checked against it from then on.
Questions about get_notification_preferences
Get current notification preference toggles (booking reminders, payment reminders, quote follow-ups, etc.). It is categorised as a Read tool in the Businys MCP Server, which means it retrieves data without modifying state.
Register the Businys MCP server in PolicyLayer and add a rule for get_notification_preferences: 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.
get_notification_preferences 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_notification_preferences 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_notification_preferences. 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_notification_preferences 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