List available Obsidian commands. Optionally filter by plugin name (e.g.,
AI agents call command_list to retrieve information from Connect MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that enumerates commands available in Obsidian, similar to a help or introspection API. No side effects, no data modification, no execution. It is informational only. Low severity because the blast radius is minimal—an agent cannot misuse this to cause harm beyond discovering what commands exist.
From the tool's definition "List available Obsidian commands" with optional filtering—retrieves a static enumeration of available commands without executing them or modifying any state.
Attacks that exploit this kind of access
List available Obsidian commands. Optionally filter by plugin name (e.g.,. It is categorised as a Read tool in the Connect MCP MCP Server, which means it retrieves data without modifying state.
Register the Connect MCP server in PolicyLayer and add a rule for command_list: 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 Connect MCP. Nothing to install.
command_list 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 command_list 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 command_list. 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.
command_list is provided by the Connect MCP server (joch/obsidian-connect-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 →