Start browser preview and open Excalidraw editor interface.\n\n
AI agents invoke start_session to trigger actions in Excalidraw 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.
This tool triggers an external operation (starting a browser process and opening an editor interface). While the operation itself is not inherently harmful and does not modify data, it executes a command whose side effects are not fully reversible or under direct control.
From the tool's definition Tool description states it will 'Start browser preview and open Excalidraw editor interface' — this involves launching an external operation (browser process) whose effects depend on context.
Documented attack patterns abuse exactly the kind of access start_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excalidraw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_session:
{
"version": "1",
"default": "deny",
"tools": {
"start_session": {
"limits": [
{
"counter": "start_session_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} start_session 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.
Start browser preview and open Excalidraw editor interface.\n\n. It is categorised as a Execute tool in the Excalidraw MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Excalidraw MCP Server MCP server in PolicyLayer and add a rule for start_session: 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 Excalidraw MCP Server. Nothing to install.
start_session 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 start_session 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 start_session. 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.
start_session is provided by the Excalidraw MCP Server MCP server (scofieldfree/excalidraw-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Excalidraw MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Excalidraw MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.