Medium Risk

deployments_upload

Deploy a static site instantly. 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.

Accepts file system path (path)

Part of the ShipStatic MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@shipstatic/mcp Write Risk 3/5

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. Intercept'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.

shipstatic.yaml
tools:
  deployments_upload:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full ShipStatic policy for all 15 tools.

Tool Name deployments_upload
Category Write
Risk Level Medium

View all 15 tools →

Agents calling write-class tools like deployments_upload have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the deployments_upload tool do? +

Deploy a static site instantly. 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.. 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.

How do I enforce a policy on deployments_upload? +

Add a rule in your Intercept YAML policy under the tools section for deployments_upload. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ShipStatic MCP server.

What risk level is deployments_upload? +

deployments_upload is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit deployments_upload? +

Yes. Add a rate_limit block to the deployments_upload rule in your Intercept 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.

How do I block deployments_upload completely? +

Set action: deny in the Intercept 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.

What MCP server provides deployments_upload? +

deployments_upload is provided by the ShipStatic MCP server (@shipstatic/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ShipStatic

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.