obsidian-mcp-list-schemas
AI agents call obsidian-mcp-list-schemas to retrieve information from Vault MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve and display available schemas without modifying data. Listing operations are read-only queries with no side effects or blast radius. The semantic similarity to 'list-files' (a pure enumeration operation) and the verb 'list' strongly suggest a retrieval function. Even in the Obsidian context with its file-based architecture, enumerating available schemas is a low-risk read operation.
From the tool's definition Tool name 'list-schemas' indicates a retrieval operation that enumerates or displays schema definitions. The tool name structure (list-*) is consistent with other Read tools on the server like 'list-files'.
Documented attack patterns abuse exactly the kind of access obsidian-mcp-list-schemas gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vault MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian-mcp-list-schemas:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian-mcp-list-schemas": {}
}
}obsidian-mcp-list-schemas 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.
obsidian-mcp-list-schemas. It is categorised as a Read tool in the Vault MCP MCP Server, which means it retrieves data without modifying state.
Register the Vault MCP server in PolicyLayer and add a rule for obsidian-mcp-list-schemas: 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 Vault MCP. Nothing to install.
obsidian-mcp-list-schemas 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 obsidian-mcp-list-schemas 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 obsidian-mcp-list-schemas. 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.
obsidian-mcp-list-schemas is provided by the Vault MCP server (jlevere/obsidian-mcp-plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vault MCP, 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.
8 Vault MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.