AI agents use magnyxa_publish_site to create or update resources in Magnyxa — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Magnyxa environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | 公開するプロジェクトのID（ユーザーから提供される） |
custom_css | string | — | 公開するCSSスタイル（任意） |
custom_html | string | Yes | 公開するHTMLコンテンツ（完全なHTMLドキュメント推奨） |
custom_slug | string | — | カスタムURL slug（任意、指定しない場合は自動生成） |
Parameters from the server's own tool schema.
The tool creates/publishes new web content (HTML/CSS) to a public site, which is a reversible Write operation. While publishing affects external visibility, it does not permanently delete data or execute arbitrary code—it creates structured content.
From the tool's definition Tool name 'magnyxa_publish_site' and description state it creates and publishes a new project site by specifying HTML and CSS to create a public site ('公開サイトを作成します'). This is a reversible creation action that modifies the published state of a project.
Attacks that exploit this kind of access
プロジェクトのサイトを新規公開します（初回公開用）。HTMLとCSSを指定して、公開サイトを作成します。既にサイトが公開されている場合（is_public=true）は、代わりに magnyxa_update_site を使用してください。事前にmagnyxa_set_tokenでトークンを設定する必要があります。. It is categorised as a Write tool in the Magnyxa MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
magnyxa_publish_site accepts 4 parameters: app_id, custom_css, custom_html, custom_slug. Required: app_id, custom_html. The full parameter table on this page comes from the server's own tool schema.
Register the Magnyxa MCP server in PolicyLayer and add a rule for magnyxa_publish_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 Magnyxa. Nothing to install.
magnyxa_publish_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 magnyxa_publish_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 magnyxa_publish_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.
magnyxa_publish_site is provided by the Magnyxa MCP server (@zelklab/magnyxa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →