Assign a workflow step to a specific user
AI agents use smartling_assign_workflow_step to create or update resources in Smartling MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Smartling MCP Server environment.
The tool modifies workflow assignments by assigning steps to users. This is reversible (assignments can be changed or reassigned), making it a Write operation rather than Execute or Destructive. The severity is medium because misassignment could disrupt translation workflows, delay content delivery, or cause process inefficiencies, but it doesn't delete data, execute arbitrary code, or move money.
From the tool's definition Tool name 'assign_workflow_step' and description 'Assign a workflow step to a specific user' indicate modifying workflow state by assigning tasks to users. This is a write operation that creates or updates workflow assignments.
Attacks that exploit this kind of access
Assign a workflow step to a specific user. It is categorised as a Write tool in the Smartling MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Smartling MCP Server MCP server in PolicyLayer and add a rule for smartling_assign_workflow_step: 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 Smartling MCP Server. Nothing to install.
smartling_assign_workflow_step 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 smartling_assign_workflow_step 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 smartling_assign_workflow_step. 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.
smartling_assign_workflow_step is provided by the Smartling MCP Server MCP server (jacobolevy/smartling-mcp-server). 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 →