Detect context and generate clarifying questions before storing knowledge. Use this when palace_store intent is incomplete or ambiguous. Returns: - Detected context (capture_type, domains, projects, clients) - Questions to ask the user for missing information - Suggestions based on detection with...
AI agents call palace_clarify 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.
palace_clarify is a utility that analyzes input to detect context and generates clarifying questions before data storage occurs. It performs pattern detection and returns informational output (questions, suggestions, confidence scores) without creating, modifying, deleting, or executing operations.
From the tool's definition Tool description states it "Detect[s] context and generate[s] clarifying questions" and "Returns: Detected context, Questions to ask the user for missing information, Suggestions based on detection." The verb phrases describe analysis and question generation…
Attacks that exploit this kind of access
Detect context and generate clarifying questions before storing knowledge. Use this when palace_store intent is incomplete or ambiguous. Returns: - Detected context (capture_type, domains, projects, clients) - Questions to ask the user for missing information - Suggestions based on detection with confidence scores Capture Types (Phase 017): -. It is categorised as a Read tool in the Obsidian Palace MCP MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_clarify: 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.
palace_clarify 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 palace_clarify 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 palace_clarify. 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.
palace_clarify 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.
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 →