AI agents use add_file_to_matter to create or update resources in Smokeball — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smokeball environment.
This tool creates or registers new files associated with a legal matter in a law firm practice management system (Smokeball). While not destructive or executable, it modifies persistent data by adding file records to a matter. In a law firm context, incorrectly filed documents could cause operational and compliance issues, justifying high severity.
From the tool's definition Tool description states 'Register a new file on a matter' — this creates a new file record in the system, modifying matter data. The word 'Register' and 'new file' indicate a creation/write operation.
Attacks that exploit this kind of access
Register a new file on a matter (get upload URL separately). It is categorised as a Write tool in the Smokeball MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smokeball MCP server in PolicyLayer and add a rule for add_file_to_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.
add_file_to_matter 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 add_file_to_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 add_file_to_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.
add_file_to_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 →