AI agents use create_case_message_thread 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 creates a new message thread, which is a reversible write operation. It modifies the case by adding communication records but does not execute arbitrary code, delete data, or move money. The blast radius is moderate because misconfigured message threads could expose sensitive client information or create incorrect case communications, but the action can be undone or corrected.
From the tool's definition Tool name contains 'create' and description states 'Create a message thread on a case', indicating data creation without irreversible deletion or financial impact.
Attacks that exploit this kind of access
Create a message thread on a case. client_ids/staff_ids: comma-separated IDs. 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 create_case_message_thread: 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.
create_case_message_thread 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 create_case_message_thread 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 create_case_message_thread. 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.
create_case_message_thread 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 →