# render

Compile and export the document.

Agent View of the PolicyLayer registry record for `render`. HTML page: https://policylayer.com/tools/aaronsb-texflow-mcp/render

## Facts

- Tool: `render`
- Server: TeXFlow (`aaronsb/texflow-mcp`) — https://policylayer.com/tools/aaronsb-texflow-mcp.md
- Homepage: https://github.com/aaronsb/texflow-mcp
- Risk category: Execute (High risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "render",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches TeXFlow:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "render": {
      "limits": [
        {
          "counter": "render_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on TeXFlow (5)

- `document` — Other — https://policylayer.com/tools/aaronsb-texflow-mcp/document.md
- `queue` — Other — https://policylayer.com/tools/aaronsb-texflow-mcp/queue.md
- `reference` — Other — https://policylayer.com/tools/aaronsb-texflow-mcp/reference.md
- `edit` — Write — https://policylayer.com/tools/aaronsb-texflow-mcp/edit.md
- `layout` — Write — https://policylayer.com/tools/aaronsb-texflow-mcp/layout.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aaronsb-texflow-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aaronsb-texflow-mcp