List all available commands in Obsidian. For commands that operate on notes, open a note first.
AI agents call list_commands to retrieve information from Obsidian Modified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and displays information about available Obsidian commands. It does not execute commands, create, modify, or delete data. It is a straightforward read operation that returns a static or nearly-static list of available functionality. The low severity reflects minimal blast radius if misused — listing commands cannot harm data or systems.
From the tool's definition Tool description states it 'List[s] all available commands in Obsidian' — a pure enumeration/query operation with no side effects. The note about opening notes first is instructional, not indicative of mutation.
Attacks that exploit this kind of access
List all available commands in Obsidian. For commands that operate on notes, open a note first. It is categorised as a Read tool in the Obsidian Modified MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Modified MCP server in PolicyLayer and add a rule for list_commands: 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 Modified. Nothing to install.
list_commands 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 list_commands 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 list_commands. 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.
list_commands is provided by the Obsidian Modified MCP server (@marwansaab/obsidian-modified-mcp-server). 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 →