AI agents use create_canvas to create or update resources in Obsidian MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian MCP Server environment.
This tool creates new canvas files in the Obsidian vault. It is a reversible Write operation (files can be deleted or modified later). Severity is medium because creating files can impact vault organization and consume storage, but the effect is limited to the user's local vault and is easily undoable. Confidence is high because the description clearly indicates file creation without ambiguity.
From the tool's definition Tool name: 'create_canvas'; description: 'Create a new canvas JSON file'. The verb 'Create' and action of generating a new file indicate data creation.
Documented attack patterns abuse exactly the kind of access create_canvas gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_canvas:
{
"version": "1",
"default": "deny",
"tools": {
"create_canvas": {
"limits": [
{
"counter": "create_canvas_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_canvas stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new canvas JSON file. It is categorised as a Write tool in the Obsidian MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for create_canvas: 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 Obsidian MCP Server. Nothing to install.
create_canvas is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_canvas 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 create_canvas. 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.
create_canvas is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian 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.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.