P93 — admin escape hatch. Forces a proof_ledger row's measurement_due_at into the past so the cron's next tick picks it up. USE WHEN smoke testing the launch → measure → next-move chain without waiting 24h, OR an ops user needs to retry a stuck measurement. Gated by CHIEFLAB_ADMIN_TOKEN header (s...
Risk signalsAdmin/system-level operation
Part of the ChiefLab server.
Free to start. No card required.
AI agents may call chieflab_force_measurement_due to permanently remove or destroy resources in ChiefLab. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call chieflab_force_measurement_due in a loop, permanently destroying resources in ChiefLab. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"chieflab_force_measurement_due"
]
}See the full ChiefLab policy for all 45 tools.
These attack patterns abuse exactly the kind of access chieflab_force_measurement_due gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
P93 — admin escape hatch. Forces a proof_ledger row's measurement_due_at into the past so the cron's next tick picks it up. USE WHEN smoke testing the launch → measure → next-move chain without waiting 24h, OR an ops user needs to retry a stuck measurement. Gated by CHIEFLAB_ADMIN_TOKEN header (same gate as /api-keys/issue). Refuses if the row is already measured. Pass dueAt (ISO string) to set a specific time; defaults to now - 60s.. It is categorised as a Destructive tool in the ChiefLab MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ChiefLab MCP server in PolicyLayer and add a rule for chieflab_force_measurement_due: 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 ChiefLab. Nothing to install.
chieflab_force_measurement_due is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the chieflab_force_measurement_due 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 chieflab_force_measurement_due. 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.
chieflab_force_measurement_due is provided by the ChiefLab MCP server (@chieflab/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 ChiefLab tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.