Mark today's matching HabitTracker habit complete.
AI agents use complete_habit to create or update resources in Poke HabitTracker MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Poke HabitTracker MCP environment.
This tool modifies data (marking a habit as complete) but the change is reversible via the sibling 'uncomplete_habit' tool, making it Write rather than Destructive. The blast radius is low because misuse only affects personal habit tracking data with no financial, cascading, or external system impacts.
From the tool's definition Tool name 'complete_habit' and description 'Mark today's matching HabitTracker habit complete' indicate the tool creates or modifies data reversibly by updating the completion status of a habit record in Supabase.
Attacks that exploit this kind of access
Mark today's matching HabitTracker habit complete. It is categorised as a Write tool in the Poke HabitTracker MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Poke HabitTracker MCP server in PolicyLayer and add a rule for complete_habit: 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 Poke HabitTracker MCP. Nothing to install.
complete_habit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_habit 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 complete_habit. 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.
complete_habit is provided by the Poke HabitTracker MCP server (smoothiekanoble/poke-mcp). 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 →