# revoke_flyer

Take down a flyer immediately: the link starts returning "gone" and the stored document is deleted. Needs the id and owner_token returned when it was published — there are no accounts, so that token is the only proof of ownership and it is not recoverable if lost.

Agent View of the PolicyLayer registry record for `revoke_flyer`. HTML page: https://policylayer.com/tools/com-flingflyers-flingflyers/revoke-flyer

## Facts

- Tool: `revoke_flyer`
- Server: Flingflyers (`https://flingflyers.com/mcp`) — https://policylayer.com/tools/com-flingflyers-flingflyers.md
- Homepage: https://github.com/https://flingflyers.com/mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | The flyer id, e.g. x7Kp2mQ. |
| `owner_token` | string | yes | The owner_token returned by publish_flyer. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "revoke_flyer",
    "arguments": {
      "id": "<id>",
      "owner_token": "<owner_token>"
    }
  }
}
```

## Why revoke_flyer is rated Critical

This tool irreversibly deletes stored documents and makes shared links permanently inaccessible. While it requires an owner_token for authorization, a misused revoke_flyer call would permanently erase a published document with no recovery path.

From the tool's own definition: "Tool description states: 'the link starts returning 'gone' and the stored document is deleted.' This is an irreversible deletion operation. The tool name 'revoke_flyer' and description 'Take down a flyer immediately' confirm the destructive action."

## Use case

AI agents call revoke_flyer to permanently remove resources in Flingflyers, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Flingflyers:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_flyer"
  ]
}
```

## Other tools on Flingflyers (2)

- `publish_flyer` — Write — https://policylayer.com/tools/com-flingflyers-flingflyers/publish-flyer.md
- `update_flyer` — Write — https://policylayer.com/tools/com-flingflyers-flingflyers/update-flyer.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-flingflyers-flingflyers · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-flingflyers-flingflyers