Add an entry to the current session log. Use this to track what you
AI agents use palace_session_log to create or update resources in Obsidian Palace MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obsidian Palace MCP environment.
This tool creates new data (log entries) but does not execute arbitrary code, trigger external operations, delete data, or move money. The modification is reversible—entries can be amended or cleared.
From the tool's definition Tool name 'palace_session_log' and description 'Add an entry to the current session log' indicate the tool creates or appends new log entries, which is a reversible write operation.
Attacks that exploit this kind of access
Add an entry to the current session log. Use this to track what you. It is categorised as a Write tool in the Obsidian Palace MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_session_log: 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_session_log is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the palace_session_log 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_session_log. 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_session_log 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 →