paper_revoke_share
Revoke a Paper share link. Live writes require dryRun:false, approved:true, reason, and idempotencyKey.
This record as markdown: /tools/adrata-starfield-mcp/paper-revoke-share.md
What paper_revoke_share does on Starfield
AI agents call paper_revoke_share to permanently remove resources in Starfield, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
dryRun | boolean | — | Defaults to true. Set false only after explicit user approval. |
reason | string | — | Audit reason for live writes. |
shareId | string | Yes | |
approved | boolean | — | Must be true for live writes. |
idempotencyKey | string | — | Required for live writes. |
Parameters from the server's own tool schema.
Why paper_revoke_share is rated Critical
An AI agent that decides to call paper_revoke_share doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Starfield is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs paper_revoke_share safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For paper_revoke_share, this is the rule to start with:
paper_revoke_share is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Starfield, apply this rule, and every paper_revoke_share call is checked against it from then on.
Questions about paper_revoke_share
Revoke a Paper share link. Live writes require dryRun:false, approved:true, reason, and idempotencyKey. It is categorised as a Destructive tool in the Starfield MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
paper_revoke_share accepts 5 parameters: dryRun, reason, shareId, approved, idempotencyKey. Required: shareId. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for paper_revoke_share: 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 Starfield. Nothing to install.
paper_revoke_share 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 paper_revoke_share 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 paper_revoke_share. 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.
paper_revoke_share is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
Across the catalogue