# 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 -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.
Agent View of the PolicyLayer registry record for `publish_flyer`. HTML page: https://policylayer.com/tools/com-flingflyers-flingflyers/publish-flyer
## Facts
- Tool: `publish_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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 2 (1 required)
- Recommended policy verdict: Rate-limited
## Parameters
| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `html` | string | yes | The complete HTML document, including . Must be self-contained. |
| `ttl_hours` | integer | no | How long the link should live, in hours. Default 168 (7 days), maximum 720 (30 days). |
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": "publish_flyer",
"arguments": {
"html": ""
}
}
}
```
## 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 own 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 signals: Accepts raw HTML/template content (html)
## Use case
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.
## Recommended policy (PolicyLayer)
Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Flingflyers:
```json
{
"version": "1",
"default": "deny",
"tools": {
"publish_flyer": {
"limits": [
{
"counter": "publish_flyer_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}
```
## Other tools on Flingflyers (2)
- `revoke_flyer` — Destructive — https://policylayer.com/tools/com-flingflyers-flingflyers/revoke-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