List checkin records for a habit.
AI agents call dida365_list_habit_checkins to retrieve information from Dida365 Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical check-in records for habits, which is a read-only query operation. It does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an agent could only view habit history data, which has no security or operational impact.
From the tool's definition Tool name 'list_habit_checkins' and description 'List checkin records for a habit' indicate data retrieval without modification. No side effects or irreversible actions are performed.
Attacks that exploit this kind of access
List checkin records for a habit. It is categorised as a Read tool in the Dida365 Agent MCP Server, which means it retrieves data without modifying state.
Register the Dida365 Agent MCP server in PolicyLayer and add a rule for dida365_list_habit_checkins: 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 Dida365 Agent. Nothing to install.
dida365_list_habit_checkins 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 dida365_list_habit_checkins 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 dida365_list_habit_checkins. 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.
dida365_list_habit_checkins is provided by the Dida365 Agent MCP server (linhai0872/dida365-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →