autopilot_zero_touch_metrics
Reads AutoPilot ledger rows and returns zero-touch scoring. Use before closing a canary or claiming human_touch_count=0.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/autopilot-zero-touch-metrics.md
What autopilot_zero_touch_metrics does on UnClick
AI agents call autopilot_zero_touch_metrics to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum recent ledger rows to scan. |
ref_id | string | — | Optional object id filter. |
ref_kind | string | — | Optional object type filter. |
Parameters from the server's own tool schema.
Why autopilot_zero_touch_metrics is rated Low
This tool performs a read operation on existing ledger data and computes/returns a metric (zero-touch scoring). It has no capability to modify, delete, execute external operations, or create financial transactions. The purpose is informational—supporting decision-making before closing canaries. No destructive, write, execute, or financial operations are described.
From the tool's definition Tool description explicitly states 'Reads AutoPilot ledger rows and returns zero-touch scoring.' The verb 'reads' combined with 'returns' indicates data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs autopilot_zero_touch_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For autopilot_zero_touch_metrics, this is the rule to start with:
autopilot_zero_touch_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every autopilot_zero_touch_metrics call is checked against it from then on.
Questions about autopilot_zero_touch_metrics
Reads AutoPilot ledger rows and returns zero-touch scoring. Use before closing a canary or claiming human_touch_count=0. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
autopilot_zero_touch_metrics accepts 3 parameters: limit, ref_id, ref_kind. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for autopilot_zero_touch_metrics: 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 UnClick. Nothing to install.
autopilot_zero_touch_metrics 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 autopilot_zero_touch_metrics 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 autopilot_zero_touch_metrics. 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.
autopilot_zero_touch_metrics is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue