AI agents use put_object_text 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.
This tool creates or modifies objects in S3 storage, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely query data (Read). The medium severity reflects that misuse could corrupt or overwrite important data in storage, but the operation itself is reversible and the blast radius is limited to the objects being written.
From the tool's definition Tool name is 'put_object_text' and description states 'Write a UTF-8 text object', which creates or modifies data in S3-compatible object storage.
Attacks that exploit this kind of access
Write a UTF-8 text object. (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.
Register the Rustfs MCP server in PolicyLayer and add a rule for put_object_text: 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.
put_object_text is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the put_object_text 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 put_object_text. 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.
put_object_text 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 →