remove_bucket_notification · Rustfs MCP: Risk & Policy

WHAT IT DOES

What remove_bucket_notification does on Rustfs

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

WHY IT NEEDS A POLICY

Why remove_bucket_notification needs a policy

This tool removes/disables bucket notification configuration. While it modifies a setting (Write), it does not delete data objects or buckets themselves. However, disabling notifications can cause loss of event visibility and potentially break downstream integrations or alerting pipelines, making misuse high severity. The note about being refused on production add-ons signals awareness of its impact.

From the tool's definition Stop emitting this bucket's events. (Refused on read-only / production add-ons.)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_bucket_notification Rate-limited

remove_bucket_notification 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": {
    "remove_bucket_notification": {
      "limits": [
        {
          "counter": "remove_bucket_notification_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 Rustfs, so you can run agents against it safely.

FAQ

Questions about remove_bucket_notification

What does the remove_bucket_notification tool do? +

Stop emitting this bucket's events. (Refused on read-only / production add-ons.). It is categorised as a Write tool in the Rustfs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on remove_bucket_notification? +

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

What risk level is remove_bucket_notification? +

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

Can I rate-limit remove_bucket_notification? +

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

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

remove_bucket_notification is provided by the Rustfs MCP server (stackblaze/rustfs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.