log_judgment_call
AI agents use log_judgment_call to create or update resources in Claude Operator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Operator environment.
The tool likely creates or modifies log/judgment records in the operator's memory system (consistent with sibling tools like 'update_memory' and 'search_memory'). While a pure read would not justify Write classification, the verb 'log' typically implies recording/persistence.
From the tool's definition Tool name 'log_judgment_call' suggests recording or storing a decision/judgment; the context of a memory-managed autonomous operator implies writing to a persistent store. The description is empty, reducing certainty.
Attacks that exploit this kind of access
log_judgment_call. It is categorised as a Write tool in the Claude Operator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Operator MCP server in PolicyLayer and add a rule for log_judgment_call: 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 Claude Operator. Nothing to install.
log_judgment_call 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 log_judgment_call 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 log_judgment_call. 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.
log_judgment_call is provided by the Claude Operator MCP server (moygulati/claude-operator). 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 →