AI agents call list_client_message_threads to retrieve information from Mycase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation that retrieves message thread data for a specific client. It queries existing information without creating, modifying, deleting, or executing any actions. The low severity reflects that message threads are typically non-sensitive communications within a law firm's internal systems, and listing them poses minimal risk even if accessed by an unauthorized agent.
From the tool's definition Tool name contains 'list' and description states 'List all message threads for a client' — retrieves and queries existing message threads without modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
List all message threads for a client. It is categorised as a Read tool in the Mycase MCP Server, which means it retrieves data without modifying state.
Register the Mycase MCP server in PolicyLayer and add a rule for list_client_message_threads: 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.
list_client_message_threads 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 list_client_message_threads 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 list_client_message_threads. 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.
list_client_message_threads 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 →