diagram_create
Create professional diagrams using Eraser.io. Use when user mentions /eraser, 'eraser', 'create a diagram with eraser', or when complex information would benefit from visual representation. Supports ONLY: flowchart, sequence-diagram, cloud-architecture-diagram, entity-relationship-diagram.
This record as markdown: /tools/0xcjt-templonixlite/diagram-create.md
What diagram_create does on Templonix Lite MCP Server
AI agents invoke diagram_create to trigger actions in Templonix Lite 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.
Why diagram_create is rated High
The tool invokes an external service (Eraser.io) to generate diagrams, which constitutes triggering an external operation rather than a simple local write. The blast radius is medium since it interacts with a third-party platform but produces diagrams rather than moving money or deleting data.
From the tool's definition 'Create professional diagrams using Eraser.io' — triggers an external operation on a third-party service (Eraser.io)
Attacks that exploit this kind of access
The rule that runs diagram_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Templonix Lite MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For diagram_create, this is the rule to start with:
diagram_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Templonix Lite MCP Server, apply this rule, and every diagram_create call is checked against it from then on.
Questions about diagram_create
Create professional diagrams using Eraser.io. Use when user mentions /eraser, 'eraser', 'create a diagram with eraser', or when complex information would benefit from visual representation. Supports ONLY: flowchart, sequence-diagram, cloud-architecture-diagram, entity-relationship-diagram. It is categorised as a Execute tool in the Templonix Lite MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Templonix Lite MCP Server MCP server in PolicyLayer and add a rule for diagram_create: 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 Templonix Lite MCP Server. Nothing to install.
diagram_create 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 diagram_create 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 diagram_create. 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.
diagram_create is provided by the Templonix Lite MCP Server MCP server (0xcjt/templonixlite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Templonix Lite MCP Server, and thousands of servers like it.
Across the catalogue