# update_flyer Replace the contents of a flyer you already published, keeping the same URL. Use this for every revision to a page that is already live — a fix, a new section, a chart the user asked you to add — so the link they may have already sent to someone keeps working and shows the new version. Prefer this over publishing again. A second publish_flyer call mints a different URL and leaves the old page live and out of date, which is almost never what the user meant by "update it". Needs the id and owner_token returned when it was published; there are no accounts, so that token is the only proof of ownership. Send the complete replacement document, not a patch or a fragment — the old contents are overwritten and cannot be recovered. The expiry is left alone unless you pass ttl_hours, so editing a page does not quietly extend how long its link stays alive. Agent View of the PolicyLayer registry record for `update_flyer`. HTML page: https://policylayer.com/tools/com-flingflyers-flingflyers/update-flyer ## Facts - Tool: `update_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: 4 (3 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `id` | string | yes | The flyer id, e.g. x7Kp2mQ. | | `html` | string | yes | The complete replacement HTML document, including . Must be self-contained. | | `ttl_hours` | integer | no | Optional. Reset the expiry to this many hours from now, maximum 720 (30 days). Omit to keep the flyer's existing expiry. | | `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": "update_flyer", "arguments": { "id": "", "html": "", "owner_token": "" } } } ``` ## Why update_flyer is rated Medium This tool modifies existing data (flyer contents) reversibly without deleting anything. It's a standard update operation. Severity is medium because: (1) it modifies publicly-shared content that may have been distributed, potentially affecting downstream users; (2) the description emphasizes this keeps 'the same URL', meaning changes are invisible to link recipients; (3) however, the owner token acts as a mitigating… From the tool's own definition: "Tool description states 'Replace the contents of a flyer you already published' and 'for every revision to a page that is already live' — these are classic modify/update operations." Risk signals: Accepts raw HTML/template content (html) · Bulk/mass operation — affects multiple targets ## Use case AI agents use update_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": { "update_flyer": { "limits": [ { "counter": "update_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 - `publish_flyer` — Write — https://policylayer.com/tools/com-flingflyers-flingflyers/publish-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