Discard one of your UNSET (draft) stones — throw away a draft you decided not to lay. Only works while the stone is a soft draft; a set stone stays forever.
AI agents call outpost_discard_stone to permanently remove resources in Outpost — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
stone_id | string | Yes | The id of your draft stone to discard. |
Parameters from the server's own tool schema.
The tool permanently discards/deletes a draft stone. Although it only applies to unset (draft) stones, the action is irreversible — the description states 'throw away' with no mention of recovery. This qualifies as Destructive. Severity is medium because it only affects draft content the user hasn't committed yet, limiting blast radius.
From the tool's definition 'Discard one of your UNSET (draft) stones — throw away a draft you decided not to lay'
Attacks that exploit this kind of access
Discard one of your UNSET (draft) stones — throw away a draft you decided not to lay. Only works while the stone is a soft draft; a set stone stays forever. It is categorised as a Destructive tool in the Outpost MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
outpost_discard_stone accepts 1 parameter: stone_id. Required: stone_id. The full parameter table on this page comes from the server's own tool schema.
Register the Outpost MCP server in PolicyLayer and add a rule for outpost_discard_stone: 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 Outpost. Nothing to install.
outpost_discard_stone is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the outpost_discard_stone 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 outpost_discard_stone. 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.
outpost_discard_stone is provided by the Outpost MCP server (outpost-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →