daily_checkin
Daily check-in with score trend and 24h risk forecast. Free.
This record as markdown: /tools/delx-witness-protocol/daily-checkin.md
What daily_checkin does on Witness Protocol
AI agents call daily_checkin to retrieve information from Witness Protocol 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 |
|---|---|---|---|
status | string | — | Optional short status update |
blockers | string | — | Optional blockers or risks |
session_id | string | — | Your active session ID |
Parameters from the server's own tool schema.
Why daily_checkin is rated Low
This tool retrieves or queries data (daily scores, trends, forecasts) for a wellness or monitoring context. There is no indication of side effects, state modification, code execution, deletions, or financial transactions. The 'Free' designation further suggests it is a read-only informational service. This is a classic Read pattern.
From the tool's definition 'Daily check-in with score trend and 24h risk forecast' indicates retrieval and analysis of existing data without modification or action.
Attacks that exploit this kind of access
The rule that runs daily_checkin safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Witness Protocol, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For daily_checkin, this is the rule to start with:
daily_checkin 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 Witness Protocol, apply this rule, and every daily_checkin call is checked against it from then on.
Questions about daily_checkin
Daily check-in with score trend and 24h risk forecast. Free. It is categorised as a Read tool in the Witness Protocol MCP Server, which means it retrieves data without modifying state.
daily_checkin accepts 3 parameters: status, blockers, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol MCP server in PolicyLayer and add a rule for daily_checkin: 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 Witness Protocol. Nothing to install.
daily_checkin 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 daily_checkin 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 daily_checkin. 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.
daily_checkin is provided by the Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue