AI agents call get_bucket_notification to retrieve information from Rustfs without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing event-notification rules configured on an S3 bucket. It performs no data modification, deletion, or execution of external operations—only querying and presenting current notification configuration. The blast radius if misused (e.g., exposing notification targets) is limited to information disclosure, making it a low-severity Read operation.
From the tool's definition Tool name 'get_bucket_notification' and description 'Show the bucket's event-notification rules' indicate a read-only query operation that retrieves configuration data without modification or execution of side effects.
Attacks that exploit this kind of access
Show the bucket's event-notification rules (which events → which target). It is categorised as a Read tool in the Rustfs MCP Server, which means it retrieves data without modifying state.
Register the Rustfs MCP server in PolicyLayer and add a rule for get_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.
get_bucket_notification 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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →