set_bucket_notification · Rustfs MCP: Risk & Policy

WHAT IT DOES

What set_bucket_notification does on Rustfs

AI agents use set_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 set_bucket_notification needs a policy

This tool modifies bucket configuration (notification settings) in a reversible manner. While it doesn't delete or move money, it changes system behavior by routing events to external systems. The incomplete description ('defaults' cuts off) suggests configuration of side-effects but not destructive data loss.

From the tool's definition set_bucket_notification configures bucket event emission to the kubero event bus; this modifies bucket notification settings which are persistent and affect how the system reacts to storage events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_bucket_notification Rate-limited

set_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": {
    "set_bucket_notification": {
      "limits": [
        {
          "counter": "set_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 set_bucket_notification

What does the set_bucket_notification tool do? +

Emit this bucket's object events to the kubero event bus. events defaults. 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 set_bucket_notification? +

Register the Rustfs MCP server in PolicyLayer and add a rule for set_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 set_bucket_notification? +

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

Can I rate-limit set_bucket_notification? +

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

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

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