archive_delivery

Soft-archive a delivery. Does not delete files from Google Drive.

SERVERBusinys SOURCE@businys/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/app-businys-mcp-server/archive-delivery.md

WHAT IT DOES

What archive_delivery does on Businys

AI agents use archive_delivery to create or update resources in Businys, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Businys environment.

RISK

Why archive_delivery is rated Medium

Archiving is a Write operation because it modifies data state (marks delivery as archived) but is fully reversible—deliveries can be unarchived. This is less severe than Destructive (which would permanently delete). The 'soft-archive' designation and preservation of Google Drive files confirm reversibility.

From the tool's definition Tool name 'archive_delivery' combined with description 'Soft-archive a delivery. Does not delete files from Google Drive.' indicates a reversible state change to a delivery record (archiving), with explicit confirmation it does not delete underlying data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs archive_delivery safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Businys, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_delivery, this is the rule to start with:

archive_delivery Rate-limited

archive_delivery stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_delivery": {
      "limits": [
        {
          "counter": "archive_delivery_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Businys, apply this rule, and every archive_delivery call is checked against it from then on.

FAQ

Questions about archive_delivery

What does the archive_delivery tool do? +

Soft-archive a delivery. Does not delete files from Google Drive. It is categorised as a Write tool in the Businys MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on archive_delivery? +

Register the Businys MCP server in PolicyLayer and add a rule for archive_delivery: 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 Businys. Nothing to install.

What risk level is archive_delivery? +

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

Can I rate-limit archive_delivery? +

Yes. Add a rate_limit block to the archive_delivery 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.

How do I block archive_delivery completely? +

Set action: deny in the PolicyLayer policy for archive_delivery. 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 archive_delivery? +

archive_delivery is provided by the Businys MCP server (@businys/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Businys, and thousands of servers like it.

This server

All 248 Businys tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →