Faceswap an image
AI agents invoke piapi_image_faceswap to trigger actions in MCP TS Toolkit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Face swapping is an external AI generative operation that processes and transforms images. It falls under Execute because it triggers an external operation (PiAPI.ai) with effects dependent on arguments. Severity is high due to potential misuse for creating non-consensual deepfakes or identity manipulation, which could cause significant harm.
From the tool's definition 'Faceswap an image' — triggers an external AI operation via PiAPI.ai integration that manipulates/transforms image content by swapping faces
Attacks that exploit this kind of access
Faceswap an image. It is categorised as a Execute tool in the MCP TS Toolkit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP TS Toolkit MCP server in PolicyLayer and add a rule for piapi_image_faceswap: 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 MCP TS Toolkit. Nothing to install.
piapi_image_faceswap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the piapi_image_faceswap 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 piapi_image_faceswap. 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.
piapi_image_faceswap is provided by the MCP TS Toolkit MCP server (thomas92fr/mcp-ts-toolskit). 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 →