AI agents call stat_object 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 object metadata without side effects, placing it in the Read category. Severity is medium rather than low because in an S3-compatible storage context, metadata disclosure could reveal sensitive information about objects (sizes, types, timestamps, custom metadata) that might aid reconnaissance for a subsequent attack, though the immediate risk is limited to information disclosure.
From the tool's definition Tool returns object metadata (size, content-type, etag, last-modified, user metadata) with no modification or deletion indicated. Described as 'Get' operation, which is a read-only retrieval action.
Attacks that exploit this kind of access
Get an object's metadata (size, content-type, etag, last-modified, user metadata). 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 stat_object: 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.
stat_object 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 stat_object 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 stat_object. 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.
stat_object 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 →