AI agents use create_fee 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 a new fee/time entry record in the law firm's billing system. It writes new data (a billable time entry) but is reversible in principle — the entry can typically be deleted or edited. It does not directly move money or execute code, making Write the appropriate category. Severity is medium because incorrect time entries could affect billing accuracy and client invoices.
From the tool's definition Create a fee (time entry). date: YYYY-MM-DD. duration_minutes: time spent.
Attacks that exploit this kind of access
Create a fee (time entry). date: YYYY-MM-DD. duration_minutes: time spent. 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 create_fee: 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.
create_fee 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_fee 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_fee. 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_fee 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 →