Render a consulting-quality PowerPoint presentation slide from a template. Always synchronous — one call, done. Two paths (both return 200 with pptx_url + preview_url inline, no polling): • template + params → <100ms, $0.03. No AI. Same input = same output. • template + brief → ~2s, $0.05. AI ext...
Risk signalsAccepts raw HTML/template content (template) · High parameter count (16 properties)
Part of the Slideforge server.
Free to start. No card required.
AI agents use render_slide to create or modify resources in Slideforge. 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_slide 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 Slideforge.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"render_slide": {
"limits": [
{
"counter": "render_slide_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Slideforge policy for all 13 tools.
These attack patterns abuse exactly the kind of access render_slide gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Render a consulting-quality PowerPoint presentation slide from a template. Always synchronous — one call, done. Two paths (both return 200 with pptx_url + preview_url inline, no polling): • template + params → <100ms, $0.03. No AI. Same input = same output. • template + brief → ~2s, $0.05. AI extracts params from description. Set include_pdf=true to also get a pdf_url in the response (+~150ms). Response contains signed download URLs — give these directly to the user. The pptx_url, preview_url, and pdf_url are all direct file download links. Workflow: suggest_template first → if has_good_match, use render_slide. If no template fits, use generate_slide instead.. It is categorised as a Write tool in the Slideforge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slideforge MCP server in PolicyLayer and add a rule for render_slide: 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 Slideforge. Nothing to install.
render_slide is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the render_slide 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_slide. 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_slide is provided by the Slideforge MCP server (smartdatabrokers/slideforge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Slideforge 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.