AI agents invoke convert_mermaid_to_image to trigger actions in Mermaid MCP Server. 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.
Based on the server description, this tool takes Mermaid diagram code and executes a rendering pipeline to produce image files. This is an execution of an external process (likely a headless browser or rendering engine such as Puppeteer/mermaid-cli).
From the tool's definition Tool name 'convert_mermaid_to_image' on a server described as converting Mermaid diagram code into various image formats (PNG, JPG, SVG, PDF). Description is empty.
Documented attack patterns abuse exactly the kind of access convert_mermaid_to_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mermaid MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_mermaid_to_image:
{
"version": "1",
"default": "deny",
"tools": {
"convert_mermaid_to_image": {
"limits": [
{
"counter": "convert_mermaid_to_image_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}convert_mermaid_to_image 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.
Free to start. No card required.
convert_mermaid_to_image. It is categorised as a Execute tool in the Mermaid MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mermaid MCP Server MCP server in PolicyLayer and add a rule for convert_mermaid_to_image: 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 Mermaid MCP Server. Nothing to install.
convert_mermaid_to_image 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 convert_mermaid_to_image 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 convert_mermaid_to_image. 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.
convert_mermaid_to_image is provided by the Mermaid MCP Server MCP server (wwwzhouhui/mermaid_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mermaid MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Mermaid MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.