Update a face
AI agents use dual_update_face to create or update resources in DUAL MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DUAL MCP Server environment.
The tool performs a reversible modification ('Update') to stored data, placing it in the Write category. Severity is medium because unauthorized modification of facial/identity data could enable impersonation, identity fraud, or unauthorized account takeover in a blockchain context, though the exact mechanism and scope are unclear from the minimal description.
From the tool's definition Tool name 'dual_update_face' and description 'Update a face' indicate a modification operation ('Update'). The DUAL system context suggests this likely modifies user profile or identity-related biometric/facial data associated with a blockchain account.
Attacks that exploit this kind of access
Update a face. It is categorised as a Write tool in the DUAL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DUAL MCP Server MCP server in PolicyLayer and add a rule for dual_update_face: 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 DUAL MCP Server. Nothing to install.
dual_update_face 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 dual_update_face 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 dual_update_face. 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.
dual_update_face is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-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 →