AI agents use create_canvas_group 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.
The tool creates a new grouping structure within a canvas, which modifies the canvas state but does not delete, execute code, or cause irreversible changes. Grouping is reversible (groups can be ungrouped), making it a Write-category operation. The low severity reflects minimal blast radius—misuse would only result in unwanted canvas reorganization, easily corrected by an end user.
From the tool's definition Tool name 'create_canvas_group' combined with description 'Group cards together in canvas' indicates creation and modification of canvas structure. This is a non-destructive write operation that organizes existing canvas elements.
Documented attack patterns abuse exactly the kind of access create_canvas_group 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_group:
{
"version": "1",
"default": "deny",
"tools": {
"create_canvas_group": {
"limits": [
{
"counter": "create_canvas_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_canvas_group 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.
Group cards together in canvas. 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_group: 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_group 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_group 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_group. 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_group 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.