Deploy a static site instantly — free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_API_KEY, the response includes a claim URL (site expires in 3 days) — always show both the deployment URL and claim URL to the user. To make the site private, pass passw...
Risk signalsAccepts file system path (path) · Handles credentials or secrets (password)
Part of the ShipStatic server.
Free to start. No card required.
AI agents use deployments_upload to create or modify resources in ShipStatic. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call deployments_upload repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ShipStatic.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"deployments_upload": {
"limits": [
{
"counter": "deployments_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full ShipStatic policy for all 15 tools.
These attack patterns abuse exactly the kind of access deployments_upload gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Deploy a static site instantly — free, no account or API key required. Returns the live URL, file count, and size. Without SHIP_API_KEY, the response includes a claim URL (site expires in 3 days) — always show both the deployment URL and claim URL to the user. To make the site private, pass password; always show the password to the user if you set one.. It is categorised as a Write tool in the ShipStatic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ShipStatic MCP server in PolicyLayer and add a rule for deployments_upload: 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 ShipStatic. Nothing to install.
deployments_upload 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 deployments_upload 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 deployments_upload. 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.
deployments_upload is provided by the ShipStatic MCP server (@shipstatic/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 ShipStatic tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.