archive_message
Archive (keep forever, exempt from the cap) or unarchive an inbox item. Requires handle + secret.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/archive-message.md
What archive_message does on Gateway
AI agents use archive_message to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | |
secret | string | — | |
item_id | string | Yes | |
archived | boolean | — |
Parameters from the server's own tool schema.
Why archive_message is rated Medium
This tool modifies data reversibly by changing the archive status of inbox items. While it affects data organization and retention, the action is not destructive (can be undone by unarchiving) and does not delete data. It requires authentication (handle + secret), suggesting intentional use.
From the tool's definition Tool description states it can 'Archive (keep forever, exempt from the cap) or unarchive an inbox item,' indicating modification of message state and retention properties.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs archive_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_message, this is the rule to start with:
archive_message 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every archive_message call is checked against it from then on.
Questions about archive_message
Archive (keep forever, exempt from the cap) or unarchive an inbox item. Requires handle + secret. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
archive_message accepts 4 parameters: handle, secret, item_id, archived. Required: handle, item_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for archive_message: 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 Gateway. Nothing to install.
archive_message 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 archive_message 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 archive_message. 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.
archive_message is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue