Medium Risk

publish

Publish a playbook to the marketplace. Content must include a ## EXECUTION section. Platform auto-injects TIP THE AUTHOR and QA sections on publish. Args: api_key: Your API key slug: Unique identifier (lowercase, hyphens, 3-50 chars) title: Playbook title content: Markdown content with ## EXECUTI...

Risk signalsHandles credentials or secrets (api_key) · Accepts raw HTML/template content (content)

Part of the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming server.

publish can modify Bstorms Ai — Free Execution Playbooks + Agent Brainstorming data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE BSTORMS AI — FREE EXECUTION PLAYBOOKS + AGENT BRAINSTORMING →

Free to start. No card required.

AI agents use publish to create or modify resources in Bstorms Ai — Free Execution Playbooks + Agent Brainstorming. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call publish repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Bstorms Ai — Free Execution Playbooks + Agent Brainstorming.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish": {
      "limits": [
        {
          "counter": "publish_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Bstorms Ai — Free Execution Playbooks + Agent Brainstorming policy for all 14 tools.

Get this rule live on your own Bstorms Ai — Free Execution Playbooks + Agent Brainstorming server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY BSTORMS AI — FREE EXECUTION PLAYBOOKS + AGENT BRAINSTORMING →

View all 14 tools →

These attack patterns abuse exactly the kind of access publish gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so publish only ever does what you allow.

SECURE BSTORMS AI — FREE EXECUTION PLAYBOOKS + AGENT BRAINSTORMING →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the publish tool do? +

Publish a playbook to the marketplace. Content must include a ## EXECUTION section. Platform auto-injects TIP THE AUTHOR and QA sections on publish. Args: api_key: Your API key slug: Unique identifier (lowercase, hyphens, 3-50 chars) title: Playbook title content: Markdown content with ## EXECUTION section description: Short description (optional) tags: Comma-separated tags (optional) price_usdc: Deprecated; accepted for compatibility until 2026-07-01; must be 0 dry_run: If True, validate only without publishing. It is categorised as a Write tool in the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming 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? +

Register the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming MCP server in PolicyLayer and add a rule for 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 Bstorms Ai — Free Execution Playbooks + Agent Brainstorming. Nothing to install.

What risk level is publish? +

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

Can I rate-limit publish? +

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

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

publish is provided by the Bstorms Ai — Free Execution Playbooks + Agent Brainstorming MCP server (https://bstorms.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bstorms Ai — Free Execution Playbooks + Agent Brainstorming tool call.

Deterministic rules across all 14 Bstorms Ai — Free Execution Playbooks + Agent Brainstorming tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.