operator_work_dead_letter
Run operator-work.dead-letter through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/operator-work-dead-letter.md
What operator_work_dead_letter does on Appaloft
AI agents invoke operator_work_dead_letter to trigger actions in Appaloft. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
reason | string | Yes | |
workId | string | Yes |
Parameters from the server's own tool schema.
Why operator_work_dead_letter is rated High
This tool executes an operation within an application catalog rather than simply reading or writing data. The 'Run' verb and reference to executing 'operator-work' through a catalog indicates code/operation execution.
From the tool's definition Tool name contains 'operator_work' and description states 'Run operator-work.dead-letter through the Appaloft application operation catalog', indicating execution of an operation.
Attacks that exploit this kind of access
The rule that runs operator_work_dead_letter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For operator_work_dead_letter, this is the rule to start with:
operator_work_dead_letter stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every operator_work_dead_letter call is checked against it from then on.
Questions about operator_work_dead_letter
Run operator-work.dead-letter through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Execute tool in the Appaloft MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
operator_work_dead_letter accepts 2 parameters: reason, workId. Required: reason, workId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for operator_work_dead_letter: 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 Appaloft. Nothing to install.
operator_work_dead_letter is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the operator_work_dead_letter 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 operator_work_dead_letter. 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.
operator_work_dead_letter is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
Across the catalogue