AI agents use update_call to create or update resources in Mycase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mycase environment.
This tool modifies existing call log entries by updating their resolved status, which is a reversible write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). The severity is medium because law firm call logs may contain client communications and case details, but the update is limited to status fields and is reversible.
From the tool's definition Tool name is 'update_call' and description states 'Update a call log entry' with parameter to modify 'resolved' status. The word 'Update' clearly indicates modification of existing data.
Attacks that exploit this kind of access
Update a call log entry. resolved: 'true' or 'false' to set resolved status. It is categorised as a Write tool in the Mycase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mycase MCP server in PolicyLayer and add a rule for update_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 Mycase. Nothing to install.
update_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 update_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 update_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.
update_call is provided by the Mycase MCP server (rosenadvertising/mycase-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 →