update_notification_settings

WHAT IT DOES

What update_notification_settings does on ServiceDesk Plus MCP Server

AI agents use update_notification_settings to create or update resources in ServiceDesk Plus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceDesk Plus MCP Server environment.

WHY IT NEEDS A POLICY

Why update_notification_settings needs a policy

This tool updates notification preferences or settings, which is a reversible modification operation. It does not delete data (not Destructive), does not execute arbitrary code (not Execute), does not move money (not Financial), and does not query data without side effects (not Read).

From the tool's definition Tool name 'update_notification_settings' combined with sibling tools that modify data (add_ticket_comment, add_worklog_entry, assign_request, close_request).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_notification_settings Rate-limited

update_notification_settings 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_notification_settings": {
      "limits": [
        {
          "counter": "update_notification_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceDesk Plus MCP Server, so you can run agents against it safely.

FAQ

Questions about update_notification_settings

What does the update_notification_settings tool do? +

Cập nhật cài đặt thông báo. It is categorised as a Write tool in the ServiceDesk Plus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_notification_settings? +

Register the ServiceDesk Plus MCP Server MCP server in PolicyLayer and add a rule for update_notification_settings: 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 ServiceDesk Plus MCP Server. Nothing to install.

What risk level is update_notification_settings? +

update_notification_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_notification_settings? +

Yes. Add a rate_limit block to the update_notification_settings 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.

How do I block update_notification_settings completely? +

Set action: deny in the PolicyLayer policy for update_notification_settings. 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.

What MCP server provides update_notification_settings? +

update_notification_settings is provided by the ServiceDesk Plus MCP Server MCP server (thichcode/servicedeskplus_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.