AI agents use create_portal_task 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 new data (a portal task) within the Smokeball law firm management system that is reversible—tasks can be deleted or modified. It does not execute external code, delete data irreversibly, or move money. The medium severity reflects that erroneous task creation could cause client confusion or workflow disruption, but the effect is limited in scope and reversible.
From the tool's definition Tool name 'create_portal_task' and description 'Create a client portal task' explicitly indicates creation of new data. The task becomes visible to the client, affecting information presented in the system.
Attacks that exploit this kind of access
Create a client portal task (visible to client). due_date: YYYY-MM-DD. 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_portal_task: 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_portal_task 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_portal_task 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_portal_task. 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_portal_task 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 →