merge_layout · Smokeball MCP: Risk & Policy

WHAT IT DOES

What merge_layout does on Smokeball

AI agents invoke merge_layout to trigger actions in Smokeball. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why merge_layout needs a policy

This tool runs a document generation operation by combining a template with matter data. It triggers an external operation (document generation) whose output depends on the template and data arguments. It is not purely a read operation, nor does it destructively delete data or involve financial transactions.

From the tool's definition "Execute a layout merge (generate the document from template + matter data)"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

merge_layout Rate-limited

merge_layout stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "merge_layout": {
      "limits": [
        {
          "counter": "merge_layout_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Smokeball, so you can run agents against it safely.

FAQ

Questions about merge_layout

What does the merge_layout tool do? +

Execute a layout merge (generate the document from template + matter data). It is categorised as a Execute tool in the Smokeball MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on merge_layout? +

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

What risk level is merge_layout? +

merge_layout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit merge_layout? +

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

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

merge_layout is provided by the Smokeball MCP server (rosenadvertising/smokeball-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.