render

Compile and export the document.

SERVERTeXFlow SOURCEaaronsb/texflow-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/aaronsb-texflow-mcp/render.md

WHAT IT DOES

What render does on TeXFlow

AI agents invoke render to trigger actions in TeXFlow. 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.

RISK

Why render is rated High

Rendering/compiling a document runs an external toolchain (e.g., pdflatex) and produces output files. This is an execution of an external process rather than a simple data write. The blast radius is medium: a misconfigured or malicious document could cause resource exhaustion or unexpected file system writes, but it doesn't inherently destroy data or move money.

From the tool's definition "Compile and export the document" — compiling triggers an external process (LaTeX/PDF renderer) and exporting writes output files; this is an operation whose effects depend on document content and arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs render safely

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

render Rate-limited

render 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": {
    "render": {
      "limits": [
        {
          "counter": "render_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TeXFlow, apply this rule, and every render call is checked against it from then on.

FAQ

Questions about render

What does the render tool do? +

Compile and export the document. It is categorised as a Execute tool in the TeXFlow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on render? +

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

What risk level is render? +

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

Can I rate-limit render? +

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

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

render is provided by the TeXFlow MCP server (aaronsb/texflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TeXFlow, and thousands of servers like it.

This server

All 6 TeXFlow tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →