pilotgentic_touch_id_manager

Server PilotGentic @pilotgentic/mcp-server

Category Write

Risk class Medium

Parameters 00 required

WHAT IT DOES

What pilotgentic_touch_id_manager does on PilotGentic

AI agents use pilotgentic_touch_id_manager to create or update resources in PilotGentic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PilotGentic environment.

WHY IT NEEDS A POLICY

Why pilotgentic_touch_id_manager needs a policy

An AI agent can call pilotgentic_touch_id_manager faster than any human can review — one bad instruction and it creates or modifies resources in PilotGentic by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pilotgentic_touch_id_manager Rate-limited

pilotgentic_touch_id_manager stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pilotgentic_touch_id_manager": {
      "limits": [
        {
          "counter": "pilotgentic_touch_id_manager_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PilotGentic, so you can run agents against it safely.

FAQ

Questions about pilotgentic_touch_id_manager

What does the pilotgentic_touch_id_manager tool do? +

Manage macOS Touch ID settings, enrolled fingerprints, and biometric authentication policies. Operations: get_status, list_fingerprints, check_sudo_auth, enable_sudo_auth, disable_sudo_auth, get_apple_watch_unlock, get_biometric_policy, check_secure_enclave, get_screen_lock_settings, get_pam_config. It is categorised as a Write tool in the PilotGentic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pilotgentic_touch_id_manager? +

Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_touch_id_manager: 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 PilotGentic. Nothing to install.

What risk level is pilotgentic_touch_id_manager? +

pilotgentic_touch_id_manager is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pilotgentic_touch_id_manager? +

Yes. Add a rate_limit block to the pilotgentic_touch_id_manager 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.

How do I block pilotgentic_touch_id_manager completely? +

Set action: deny in the PolicyLayer policy for pilotgentic_touch_id_manager. 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.

What MCP server provides pilotgentic_touch_id_manager? +

pilotgentic_touch_id_manager is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.