AI agents use tigris_put_object_from_path to create or update resources in Tigris — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tigris environment.
This tool creates new objects in a Tigris bucket by reading from the local filesystem and uploading to cloud storage. This is a Write operation (reversible modification) rather than Destructive, as objects can be deleted or overwritten.
From the tool's definition Tool name 'tigris_put_object_from_path' and description 'Creates an object in bucket from a path on the filesystem' indicate file upload/creation to cloud storage.
Attacks that exploit this kind of access
Creates an object in bucket from a path on the filesystem. It is categorised as a Write tool in the Tigris MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tigris MCP server in PolicyLayer and add a rule for tigris_put_object_from_path: 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 Tigris. Nothing to install.
tigris_put_object_from_path 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 tigris_put_object_from_path 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 tigris_put_object_from_path. 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.
tigris_put_object_from_path is provided by the Tigris MCP server (@tigrisdata/tigris-mcp-server). 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 →