notifications_manage · CyPerf MCP Server MCP: Risk & Policy

WHAT IT DOES

What notifications_manage does on CyPerf MCP Server

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

WHY IT NEEDS A POLICY

Why notifications_manage needs a policy

The 'manage' verb combined with 'in bulk' suggests the ability to create, update, or modify notification configurations. This is reversible (notifications can be re-configured or re-enabled), making it Write rather than Destructive. Within a network testing platform, bulk notification changes could affect alerting and monitoring visibility for multiple tests or agents, justifying medium severity.

From the tool's definition Tool name is 'notifications_manage' and description states 'Manage notifications in bulk,' indicating creation or modification of notification settings/preferences without permanent deletion.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

notifications_manage Rate-limited

notifications_manage 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": {
    "notifications_manage": {
      "limits": [
        {
          "counter": "notifications_manage_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 CyPerf MCP Server, so you can run agents against it safely.

FAQ

Questions about notifications_manage

What does the notifications_manage tool do? +

[Notifications] Manage notifications in bulk. It is categorised as a Write tool in the CyPerf 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 notifications_manage? +

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

What risk level is notifications_manage? +

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

Can I rate-limit notifications_manage? +

Yes. Add a rate_limit block to the notifications_manage 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 notifications_manage completely? +

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

notifications_manage is provided by the CyPerf MCP Server MCP server (keysight/cyperf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.