Convert Markdown or HTML to a PDF. Returns a signed download URL valid for 15 minutes.
AI agents invoke render to trigger actions in Docrenders. 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.
The tool invokes an external service to render content and produce a hosted artifact (PDF with a signed URL). This is not a simple read/query, nor does it delete data or move money. It executes an external operation whose output (a remotely stored PDF and signed URL) depends on the input arguments, placing it firmly in the Execute category.
From the tool's definition 'Convert Markdown or HTML to a PDF' and 'Returns a signed download URL valid for 15 minutes' — triggers an external API operation (DocRenders API) that generates and stores a file, producing a time-limited signed URL as a side effect.
Attacks that exploit this kind of access
Convert Markdown or HTML to a PDF. Returns a signed download URL valid for 15 minutes. It is categorised as a Execute tool in the Docrenders MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docrenders 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 Docrenders. Nothing to install.
render is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
render 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →