AI agents use tigris_upload_file_and_get_url 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/modifies data (file upload to Tigris object storage) which is reversible through deletion (tigris_delete_object exists on the server). It does not irreversibly destroy data, execute arbitrary code, or move money.
From the tool's definition Tool description states "Upload a file" which creates new data in cloud storage. The public URL generation is a secondary effect that exposes the uploaded file.
Attacks that exploit this kind of access
Upload a file and get a public url for it. 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_upload_file_and_get_url: 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_upload_file_and_get_url 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_upload_file_and_get_url 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_upload_file_and_get_url. 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_upload_file_and_get_url 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 →