palace_session_end · Obsidian Palace MCP: Risk & Policy

WHAT IT DOES

What palace_session_end does on Obsidian Palace MCP

AI agents use palace_session_end 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.

WHY IT NEEDS A POLICY

Why palace_session_end needs a policy

This tool writes session metadata (duration calculations and optional time entry records) to the Obsidian vault. While it concludes a session, the actual side effect is creating or recording time entry data, which is a write operation. It is not Read (merely closes without side effects), not Execute (doesn't run arbitrary commands), not Destructive (the time entry can be deleted), and not Financial.

From the tool's definition The tool creates a time entry (optional) which represents creating new data in the system. The description states it can 'optionally create a time entry,' indicating reversible data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

palace_session_end Rate-limited

palace_session_end stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "palace_session_end": {
      "limits": [
        {
          "counter": "palace_session_end_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Obsidian Palace MCP, so you can run agents against it safely.

FAQ

Questions about palace_session_end

What does the palace_session_end tool do? +

End the current session, calculate duration, and optionally create a time entry. Use this to close a work session started with palace_session_start. 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.

How do I enforce a policy on palace_session_end? +

Register the Obsidian Palace MCP server in PolicyLayer and add a rule for palace_session_end: 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_session_end? +

palace_session_end is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit palace_session_end? +

Yes. Add a rate_limit block to the palace_session_end 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_session_end completely? +

Set action: deny in the PolicyLayer policy for palace_session_end. 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_session_end? +

palace_session_end 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.