static_artifacts_publish

Run static-artifacts.publish through the Appaloft application operation catalog. Shared with HTTP/API.

SERVERAppaloft SOURCE@appaloft/mcp

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/appaloft-mcp/static-artifacts-publish.md

WHAT IT DOES

What static_artifacts_publish does on Appaloft

AI agents use static_artifacts_publish to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.

Parameter	Type	Required
`metadata`	object	—
`projectId`	string	Yes
`artifactId`	string	—
`resourceId`	string	Yes
`sourcePath`	string	Yes
`promoteAlias`	boolean	—

Parameters from the server's own tool schema.

RISK

Why static_artifacts_publish is rated Medium

An AI agent can call static_artifacts_publish faster than any human can review: one bad instruction and it creates or modifies resources in Appaloft by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs static_artifacts_publish safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For static_artifacts_publish, this is the rule to start with:

static_artifacts_publish Rate-limited

static_artifacts_publish 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "static_artifacts_publish": {
      "limits": [
        {
          "counter": "static_artifacts_publish_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every static_artifacts_publish call is checked against it from then on.

FAQ

Questions about static_artifacts_publish

What does the static_artifacts_publish tool do? +

Run static-artifacts.publish through the Appaloft application operation catalog. Shared with HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does static_artifacts_publish accept? +

static_artifacts_publish accepts 6 parameters: metadata, projectId, artifactId, resourceId, sourcePath, promoteAlias. Required: projectId, resourceId, sourcePath. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on static_artifacts_publish? +

Register the Appaloft MCP server in PolicyLayer and add a rule for static_artifacts_publish: 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 Appaloft. Nothing to install.

What risk level is static_artifacts_publish? +

static_artifacts_publish is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit static_artifacts_publish? +

Yes. Add a rate_limit block to the static_artifacts_publish 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.

How do I block static_artifacts_publish completely? +

Set action: deny in the PolicyLayer policy for static_artifacts_publish. 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.

What MCP server provides static_artifacts_publish? +

static_artifacts_publish is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Appaloft, and thousands of servers like it.

This server

All 358 Appaloft tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →