Check if dataview query syntax is valid
AI agents call validate_dataview_query to retrieve information from Obsidian MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read/query validation tool with no side effects. It performs static analysis on dataview query syntax without executing queries, modifying data, or triggering external operations. The blast radius of misuse is minimal since validation cannot alter state or expose sensitive data beyond what the AI already knows about syntax rules.
From the tool's definition Tool name 'validate_dataview_query' and description 'Check if dataview query syntax is valid' indicate syntax validation only. No execution, modification, or deletion occurs—it merely parses and validates query syntax.
Documented attack patterns abuse exactly the kind of access validate_dataview_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Obsidian MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_dataview_query:
{
"version": "1",
"default": "deny",
"tools": {
"validate_dataview_query": {}
}
}validate_dataview_query 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.
Check if dataview query syntax is valid. It is categorised as a Read tool in the Obsidian MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian MCP Server MCP server in PolicyLayer and add a rule for validate_dataview_query: 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 Server. Nothing to install.
validate_dataview_query 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 validate_dataview_query 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 validate_dataview_query. 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.
validate_dataview_query is provided by the Obsidian MCP Server MCP server (kynlos/obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Obsidian MCP Server, 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.
120 Obsidian MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.