Read an Obsidian canvas file (.canvas, JSON format) and return a bounded human-readable summary of its structure: total node/edge counts, up to 200 nodes with id/type/position/size/content preview, and up to 200 edges with source/target node ids plus optional label. Use to inspect or navigate a c...
AI agents call read_canvas to retrieve information from Obsidian Mcp Pro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
read_canvas retrieves and parses data from an Obsidian canvas file without altering it. It returns bounded summaries of structure and metadata. This is a pure read operation with no side effects, matching the 'Read' category (retrieves or queries data). Severity is low because exposure of canvas structure poses minimal risk; the tool cannot modify, delete, or execute arbitrary operations.
From the tool's definition Tool reads and returns a summary of canvas file structure, node/edge counts, positions, content previews, and labels. No modifications, deletions, or side effects are performed.
Documented attack patterns abuse exactly the kind of access read_canvas gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian Mcp Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for read_canvas:
{
"version": "1",
"default": "deny",
"tools": {
"read_canvas": {}
}
}read_canvas is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read an Obsidian canvas file (.canvas, JSON format) and return a bounded human-readable summary of its structure: total node/edge counts, up to 200 nodes with id/type/position/size/content preview, and up to 200 edges with source/target node ids plus optional label. Use to inspect or navigate a canvas before calling add_canvas_node or add_canvas_edge. It is categorised as a Read tool in the Obsidian Mcp Pro MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Mcp Pro MCP server in PolicyLayer and add a rule for read_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 Pro. Nothing to install.
read_canvas is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_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 read_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.
read_canvas is provided by the Obsidian Mcp Pro MCP server (rps321321/obsidian-mcp-pro). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian Mcp Pro, 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.
41 Obsidian Mcp Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.