set_day
AI agents use set_day to create or update resources in WorkTracker MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WorkTracker MCP Server environment.
The tool likely creates or modifies daily schedule data based on naming patterns and context from related tools. This is reversible (Write category) rather than destructive since 'reset_day' exists as a separate tool. Severity is medium because misuse could corrupt a user's schedule or time tracking records, but the blast radius is typically limited to one user's data. Lower confidence due to missing description.
From the tool's definition Tool name 'set_day' combined with sibling tools like 'assign_time', 'get_day', and 'reset_day' indicates this modifies schedule data. Sibling tool 'reset_day' suggests day-level state changes are possible. Description is empty, limiting confidence.
Attacks that exploit this kind of access
set_day. It is categorised as a Write tool in the WorkTracker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WorkTracker MCP Server MCP server in PolicyLayer and add a rule for set_day: 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 WorkTracker MCP Server. Nothing to install.
set_day 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 set_day 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 set_day. 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.
set_day is provided by the WorkTracker MCP Server MCP server (skytechnerds/worktracker-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 →