publish_flyer
Publish an HTML document at a short public URL and return the link. Use this when the user wants to view a page you made in a real browser, send it to someone, or open it on another device — anywhere handing back raw markup is not good enough. The link works for anyone who has it, with no account...
This record as markdown: /tools/com-flingflyers-flingflyers/publish-flyer.md
What publish_flyer does on Flingflyers
AI agents use publish_flyer to create or update resources in Flingflyers, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flingflyers environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | The complete HTML document, including <!doctype html>. Must be self-contained. |
ttl_hours | integer | — | How long the link should live, in hours. Default 168 (7 days), maximum 720 (30 days). |
Parameters from the server's own tool schema.
Why publish_flyer is rated Medium
The primary action is creating and publishing a new document at a public URL. While the operation is reversible (via sibling tool revoke_flyer), it creates a new artifact with side effects: the published content becomes publicly accessible and may be shared. This qualifies as Write rather than Read.
From the tool's definition Tool description states 'Publish an HTML document at a short public URL and return the link' — this creates a new publicly accessible resource.
Risk signalsAccepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs publish_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 publish_flyer, this is the rule to start with:
publish_flyer stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Flingflyers, apply this rule, and every publish_flyer call is checked against it from then on.
Questions about publish_flyer
Publish an HTML document at a short public URL and return the link. Use this when the user wants to view a page you made in a real browser, send it to someone, or open it on another device — anywhere handing back raw markup is not good enough. The link works for anyone who has it, with no account and no sign-in, and expires on its own (7 days by default). It is public: anyone with the URL can read the page, so do not publish anything the user would not post openly, and confirm first unless they have asked you to share it. Plain (unencrypted) only. The document reaches the server as text, so this cannot produce an encrypted flyer — for that the user runs npx flingflyers <file> -e --persist on their own machine, where the key is generated locally and never sent. Say so rather than implying this is private. Single self-contained document: inline the CSS, JS and images, or use data URIs. External file references will not resolve. It is categorised as a Write tool in the Flingflyers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
publish_flyer accepts 2 parameters: html, ttl_hours. Required: html. 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 publish_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.
publish_flyer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the publish_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 publish_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.
publish_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.
This server
Across the catalogue