update_debug_diary · Starlog MCP: Risk & Policy

WHAT IT DOES

What update_debug_diary does on Starlog

AI agents use update_debug_diary to create or update resources in Starlog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starlog environment.

WHY IT NEEDS A POLICY

Why update_debug_diary needs a policy

This tool creates or modifies debug diary records reversibly—entries can be updated, corrected, or deleted without irreversible harm. It does not execute external code, delete data permanently, or move finances. The blast radius of misuse is contained to documentation accuracy (moderate impact on project context), not system integrity or financial loss.

From the tool's definition Tool description states it will 'Log real-time discoveries, bugs, insights during work' and 'track progress and issues', indicating creation/modification of debug diary entries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_debug_diary Rate-limited

update_debug_diary 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": {
    "update_debug_diary": {
      "limits": [
        {
          "counter": "update_debug_diary_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 Starlog, so you can run agents against it safely.

FAQ

Questions about update_debug_diary

What does the update_debug_diary tool do? +

Log real-time discoveries, bugs, insights during work. Use this frequently during your work session to track progress and issues. It is categorised as a Write tool in the Starlog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_debug_diary? +

Register the Starlog MCP server in PolicyLayer and add a rule for update_debug_diary: 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 Starlog. Nothing to install.

What risk level is update_debug_diary? +

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

Can I rate-limit update_debug_diary? +

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

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

update_debug_diary is provided by the Starlog MCP server (sancovp/starlog-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.