AI agents call view_debug_diary to retrieve information from Starlog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information from a debug diary without altering state, executing code, or causing side effects. It is a pure read operation analogous to viewing logs or querying documentation. The low severity reflects minimal risk even if misused by an agent, as viewing existing data poses no destructive, financial, or operational threat.
From the tool's definition Tool description states 'Check current project status and recent entries' and 'review what's been discovered and logged during the current session' — both indicate retrieval and observation only, with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
Check current project status and recent entries. Use this to review what's been discovered and logged during the current session. It is categorised as a Read tool in the Starlog MCP Server, which means it retrieves data without modifying state.
Register the Starlog MCP server in PolicyLayer and add a rule for view_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.
view_debug_diary 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 view_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.
Set action: deny in the PolicyLayer policy for view_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.
view_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.
view_debug_diary is one line of Starlog's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →