Get the columns and tasks of a Kanban board
AI agents call get_board_content to retrieve information from Obsidian Kanban MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the structure and contents of a Kanban board (columns and tasks). It performs a read-only operation with no ability to modify, delete, or execute code. The blast radius of misuse is minimal—an AI agent could only access existing board data, not alter it or trigger external actions.
From the tool's definition Tool name 'get_board_content' and description 'Get the columns and tasks of a Kanban board' indicate data retrieval with no side effects. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
Get the columns and tasks of a Kanban board. It is categorised as a Read tool in the Obsidian Kanban MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Kanban MCP Server MCP server in PolicyLayer and add a rule for get_board_content: 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 Kanban MCP Server. Nothing to install.
get_board_content 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 get_board_content 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 get_board_content. 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.
get_board_content is provided by the Obsidian Kanban MCP Server MCP server (trung-persefoni/obsidian-kanban-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →