AI agents call detect_face_features to retrieve information from Live2D Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Face feature detection is a read-only operation that extracts information from an image without modifying, deleting, or executing arbitrary code. It returns data (detected features) with no side effects. The empty description reduces confidence slightly, but the name and server context clearly indicate a detection/analysis function rather than generation, execution, or modification.
From the tool's definition Tool name 'detect_face_features' indicates image analysis and feature detection. The server description confirms this is part of a pipeline that analyzes input photos ('analyze_photo', 'analyze_parts_with_ai' sibling tools).
Documented attack patterns abuse exactly the kind of access detect_face_features gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Live2D Automation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for detect_face_features:
{
"version": "1",
"default": "deny",
"tools": {
"detect_face_features": {}
}
}detect_face_features is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
detect_face_features. It is categorised as a Read tool in the Live2D Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Live2D Automation MCP Server MCP server in PolicyLayer and add a rule for detect_face_features: 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 Live2D Automation MCP Server. Nothing to install.
detect_face_features is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the detect_face_features 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 detect_face_features. 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.
detect_face_features is provided by the Live2D Automation MCP Server MCP server (j621111/live2d-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Live2D Automation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Live2D Automation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.