renderChart · Semiotic MCP: Risk & Policy

WHAT IT DOES

What renderChart does on Semiotic

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

WHY IT NEEDS A POLICY

Why renderChart needs a policy

Rendering a chart involves executing a graphics pipeline that transforms data into an image output. This goes beyond a simple read/query — it actively runs a rendering process with side effects (resource consumption, output generation). It does not modify stored data, but it executes a non-trivial operation whose output depends on arguments, placing it in the Execute category.

From the tool's definition 'Render a Semiotic chart to static SVG or PNG' — triggers an external rendering operation that processes input data and produces an output artifact (SVG string or Base64-encoded PNG image)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

renderChart Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Semiotic, so you can run agents against it safely.

FAQ

Questions about renderChart

What does the renderChart tool do? +

Render a Semiotic chart to static SVG or PNG. This is a static snapshot path: props must include data immediately, and ref/push-mode charts cannot be rendered through this tool. Returns SVG string (default) or Base64-encoded PNG image, plus a. It is categorised as a Execute tool in the Semiotic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on renderChart? +

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

What risk level is renderChart? +

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

Can I rate-limit renderChart? +

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

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

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