Load project context for AI session resume. Returns project status, work items, recent changes, time tracking, and more. Use depth parameter to control detail level: brief (~200-500 tokens), standard (~2K-5K tokens), deep (~8K-20K tokens). Pass project=
AI agents call palace_project_summary 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_project_summary is a read-only tool that fetches and returns project information for AI session context. It has no side effects, does not modify data, execute code, delete content, or commit financial operations. The detail level parameter only controls output verbosity, not data mutation.
From the tool's definition Tool retrieves project context, status, work items, recent changes, and time tracking information. Keywords: 'Load', 'Returns', 'control detail level' — all query operations with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Load project context for AI session resume. Returns project status, work items, recent changes, time tracking, and more. Use depth parameter to control detail level: brief (~200-500 tokens), standard (~2K-5K tokens), deep (~8K-20K tokens). Pass project=. 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_project_summary: 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_project_summary 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_project_summary 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_project_summary. 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_project_summary 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 →