palace_query

Query notes by properties like type, tags, confidence, verified status, and dates. Use this for filtering without full-text search. Supports cross-vault queries.

Server Obsidian Palace MCP probably-computers/obsidian-palace-mcp
Category Read
Risk class Low
Parameters 00 required

What palace_query does on Obsidian Palace MCP

AI agents call palace_query to retrieve information from Obsidian Palace MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why palace_query needs a policy

palace_query is a read-only tool that retrieves and filters information from the Obsidian vault based on metadata properties (type, tags, confidence, verified status, dates). It has no side effects—it does not create, modify, delete, or execute any operations. Even though it supports cross-vault queries, the scope remains informational retrieval.

From the tool's definition Tool description states 'Query notes by properties' and 'filtering without full-text search' with no mention of modifying, deleting, or executing operations. The verb 'query' combined with filtering functionality indicates data retrieval only.

Questions about palace_query

What does the palace_query tool do? +

Query notes by properties like type, tags, confidence, verified status, and dates. Use this for filtering without full-text search. Supports cross-vault queries. It is categorised as a Read tool in the Obsidian Palace MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on palace_query? +

Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_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 Palace MCP. Nothing to install.

What risk level is palace_query? +

palace_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit palace_query? +

Yes. Add a rate_limit block to the palace_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.

How do I block palace_query completely? +

Set action: deny in the PolicyLayer policy for palace_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.

What MCP server provides palace_query? +

palace_query is provided by the Obsidian Palace MCP server (probably-computers/obsidian-palace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.