Critical Risk →

render_svg

Render animated SVG from JSON config. AI controls all design parameters. Workflow: render_svg > preview > critique > revise. Iterate at least 3 times before finalizing. Element types: rect, circle, ellipse, line, polyline, polygon, path, image, text, textPath, group, use, radial-group, arc-group,...

Part of the Nakkas server.

render_svg can permanently delete data in Nakkas, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE NAKKAS →

Free to start. No card required.

AI agents may call render_svg to permanently remove or destroy resources in Nakkas. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call render_svg in a loop, permanently destroying resources in Nakkas. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "render_svg"
  ]
}

See the full Nakkas policy for all 3 tools.

Get this rule live on your own Nakkas server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY NAKKAS →

These attack patterns abuse exactly the kind of access render_svg gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so render_svg only ever does what you allow.

SECURE NAKKAS →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the render_svg tool do? +

Render animated SVG from JSON config. AI controls all design parameters. Workflow: render_svg > preview > critique > revise. Iterate at least 3 times before finalizing. Element types: rect, circle, ellipse, line, polyline, polygon, path, image, text, textPath, group, use, radial-group, arc-group, grid-group, scatter-group, path-group, parametric Pattern groups (use for repetitive designs): radial-group (circular), arc-group (arc), grid-group (matrix), scatter-group (random), path-group (along polyline). Each takes count + child element. Parametric curves (fn field): rose, heart, lissajous, spiral, star, superformula, hypotrochoid, wave. Server computes coordinates. defs: gradients (linear/radial, SMIL animated stops), filters (presets: glow, neon, blur, drop-shadow, glitch, chromatic-aberration, noise, outline, inner-shadow, emboss + 5 more), clipPaths, masks, patterns (tile fills). Animations: CSS @keyframes via animations array. Set cssClass on element matching animation name. For transforms add transformBox=. It is categorised as a Destructive tool in the Nakkas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on render_svg? +

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

What risk level is render_svg? +

render_svg is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit render_svg? +

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

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

render_svg is provided by the Nakkas MCP server (nakkas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nakkas tool call.

Deterministic rules across all 3 Nakkas 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.