reassign_workflow_task_tool
AI agents use reassign_workflow_task_tool to create or update resources in Reltio MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reltio MCP Server environment.
Based on the name, this tool likely reassigns a workflow task to a different user or group, which is a reversible write operation. However, the empty description lowers confidence. Given the server context (Reltio MDM platform with workflow tasks mentioned), reassignment is typically a Write-level operation with medium severity as it can affect business process routing.
From the tool's definition Tool name: reassign_workflow_task_tool. Description is empty and uninformative.
Attacks that exploit this kind of access
reassign_workflow_task_tool. It is categorised as a Write tool in the Reltio MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reltio MCP Server MCP server in PolicyLayer and add a rule for reassign_workflow_task_tool: 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 Reltio MCP Server. Nothing to install.
reassign_workflow_task_tool 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 reassign_workflow_task_tool 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 reassign_workflow_task_tool. 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.
reassign_workflow_task_tool is provided by the Reltio MCP Server MCP server (reltio-ai/reltio-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 →