Remove a layout instance from a matter.
AI agents call remove_layout_from_matter to permanently remove resources in Smokeball — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a layout from a matter is a destructive action that eliminates a structural configuration element from a legal case record. In a law firm context, layouts likely organize how matter data is presented and managed; removing one could cause loss of configured fields, views, or workflows associated with that matter.
From the tool's definition 'Remove a layout instance from a matter' — removal is an irreversible deletion of an association between a layout and a matter in a legal practice management system.
Attacks that exploit this kind of access
Remove a layout instance from a matter. It is categorised as a Destructive tool in the Smokeball MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Smokeball MCP server in PolicyLayer and add a rule for remove_layout_from_matter: 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 Smokeball. Nothing to install.
remove_layout_from_matter is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_layout_from_matter 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 remove_layout_from_matter. 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.
remove_layout_from_matter is provided by the Smokeball MCP server (rosenadvertising/smokeball-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 →