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.
This record as markdown: /tools/com-flingflyers-flingflyers/revoke-flyer.md
What revoke_flyer does on Flingflyers
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.
| 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.
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 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.
Attacks that exploit this kind of access
The rule that runs revoke_flyer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Flingflyers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_flyer, this is the rule to start with:
revoke_flyer 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 Flingflyers, apply this rule, and every revoke_flyer call is checked against it from then on.
Questions about 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. It is categorised as a Destructive tool in the Flingflyers MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_flyer accepts 2 parameters: id, owner_token. Required: id, owner_token. The full parameter table on this page comes from the server's own tool schema.
Register the Flingflyers MCP server in PolicyLayer and add a rule for revoke_flyer: 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 Flingflyers. Nothing to install.
revoke_flyer 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 revoke_flyer 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 revoke_flyer. 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.
revoke_flyer is provided by the Flingflyers MCP server (https://flingflyers.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Flingflyers, and thousands of servers like it.
Across the catalogue