render_template · Docrenders MCP: Risk & Policy

WHAT IT DOES

What render_template does on Docrenders

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

WHY IT NEEDS A POLICY

Why render_template needs a policy

This tool creates a new PDF document by combining a template with structured data. It is a Write operation (creates a new artifact/file) rather than Execute (no code execution or shell commands), Destructive, or Financial.

From the tool's definition Generate a PDF from a DocRenders template by passing structured data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

render_template Rate-limited

render_template 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": {
    "render_template": {
      "limits": [
        {
          "counter": "render_template_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about render_template

What does the render_template tool do? +

Generate a PDF from a DocRenders template by passing structured data. The template provides the document layout and styling. Use list_templates to see available templates and their required fields, or get_template for a specific template. It is categorised as a Write tool in the Docrenders 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_template? +

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

What risk level is render_template? +

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

Can I rate-limit render_template? +

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

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

render_template is provided by the Docrenders MCP server (jwhist/docrenders-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.