Medium Risk

render_document

Generate a document by merging a Carbone template with JSON data. Two modes: (1) pass templateId to use a previously uploaded template; (2) pass template (file path, URL, or base64) to upload and render in a single request without storing a template. Supports output format conversion, multilingua...

Risk signalsAccepts raw HTML/template content (template) · High parameter count (21 properties)

Part of the Carbone MCP server.

render_document can modify Carbone MCP data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CARBONE MCP →

Free to start. No card required.

AI agents use render_document to create or modify resources in Carbone MCP. 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 render_document 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 Carbone MCP.

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

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

See the full Carbone MCP policy for all 11 tools.

Get this rule live on your own Carbone MCP server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CARBONE MCP →

View all 11 tools →

These attack patterns abuse exactly the kind of access render_document 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 render_document only ever does what you allow.

SECURE CARBONE MCP →

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

What does the render_document tool do? +

Generate a document by merging a Carbone template with JSON data. Two modes: (1) pass templateId to use a previously uploaded template; (2) pass template (file path, URL, or base64) to upload and render in a single request without storing a template. Supports output format conversion, multilingual rendering, currency conversion, batch generation, and advanced PDF options (watermark, password, PDF/A). Async mode: pass webhookUrl to render asynchronously — Carbone will POST the renderId to your URL when the document is ready. Async mode is required when using batch generation (batchSplitBy).. It is categorised as a Write tool in the Carbone MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on render_document? +

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

What risk level is render_document? +

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

Can I rate-limit render_document? +

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

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

render_document is provided by the Carbone MCP server (https://mcp.carbone.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Carbone MCP tool call.

Deterministic rules across all 11 Carbone MCP 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.