publish_media_to_site
Publish a gallery asset as a page on the project site (media/push-to-blog). A report/HTML/text asset becomes the page
This record as markdown: /tools/ai-featureboard-featureboard/publish-media-to-site.md
What publish_media_to_site does on FeatureBoard
AI agents use publish_media_to_site to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why publish_media_to_site is rated Medium
This tool creates or modifies web pages on a site by publishing media as new pages. This is a Write operation because it creates reversible content (pages can be unpublished or deleted). Severity is medium because misuse could result in unauthorized content publication affecting the project site's public presence, but the operation is reversible.
From the tool's definition Tool description states 'Publish a gallery asset as a page on the project site' and 'asset becomes the page', indicating creation of new web content.
Attacks that exploit this kind of access
The rule that runs publish_media_to_site safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For publish_media_to_site, this is the rule to start with:
publish_media_to_site 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 FeatureBoard, apply this rule, and every publish_media_to_site call is checked against it from then on.
Questions about publish_media_to_site
Publish a gallery asset as a page on the project site (media/push-to-blog). A report/HTML/text asset becomes the page. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for publish_media_to_site: 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 FeatureBoard. Nothing to install.
publish_media_to_site 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_media_to_site 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_media_to_site. 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_media_to_site is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FeatureBoard, and thousands of servers like it.
This server
Across the catalogue