publish_recipe_bundle

Write a local, versioned recipe-bundle publish artifact: the recipe bundle JSON, a tdmcp-recipe-publish manifest, and a SHA-256 checksum manifest for repeatable handoff or CI upload.

SERVERAos SOURCE@hybridlabor-api/aos

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/publish-recipe-bundle.md

WHAT IT DOES

What publish_recipe_bundle does on Aos

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

RISK

Why publish_recipe_bundle is rated Medium

Creates versioned artifacts locally; reversible, but impacts CI/deployment pipeline integrity through publishing mechanism.

From the tool's definition Write local, versioned recipe-bundle publish artifact, JSON, manifest, SHA-256 checksum

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs publish_recipe_bundle safely

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

publish_recipe_bundle Rate-limited

publish_recipe_bundle 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": {
    "publish_recipe_bundle": {
      "limits": [
        {
          "counter": "publish_recipe_bundle_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 Aos, apply this rule, and every publish_recipe_bundle call is checked against it from then on.

FAQ

Questions about publish_recipe_bundle

What does the publish_recipe_bundle tool do? +

Write a local, versioned recipe-bundle publish artifact: the recipe bundle JSON, a tdmcp-recipe-publish manifest, and a SHA-256 checksum manifest for repeatable handoff or CI upload. It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on publish_recipe_bundle? +

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

What risk level is publish_recipe_bundle? +

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

Can I rate-limit publish_recipe_bundle? +

Yes. Add a rate_limit block to the publish_recipe_bundle 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 publish_recipe_bundle completely? +

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

publish_recipe_bundle is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

The MCP Attack Database →

Guides

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