Prepares a single-day timetable entry. Date (날짜) and work type (업무유형) are required. Project (프로젝트) is required unless the work type is NORMAL. Do not infer missing write fields from past records. If work type is missing, ask the user using the Korean labels first, not raw enum codes alone: 프로젝트 수...
AI agents use timetable.prepare_day_entry to create or update resources in Tlc Portal — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tlc Portal environment.
The tool prepares (stages) a timetable entry, which is a write operation creating or modifying timesheet data. It appears to be a preparatory step before final submission (similar to leave.prepare_request paired with leave.submit_prepared_request), so it is reversible and not yet committed.
From the tool's definition 'Prepares a single-day timetable entry' — creates/stages a timetable record requiring date, work type, and project fields; instructs on defaults and user confirmation before submission
Attacks that exploit this kind of access
Prepares a single-day timetable entry. Date (날짜) and work type (업무유형) are required. Project (프로젝트) is required unless the work type is NORMAL. Do not infer missing write fields from past records. If work type is missing, ask the user using the Korean labels first, not raw enum codes alone: 프로젝트 수행 (EXECUTE), 하자보수 (AFTER_SVC), 연구개발(R&D) (RESEARCH), 제안서 작업 (SUGGEST), 기타(일반업무) (NORMAL). If project is missing, call project.list and ask the user to choose. If hours are missing, explain that the default is 8 hours unless leave or day capacity rules reduce it. It is categorised as a Write tool in the Tlc Portal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tlc Portal MCP server in PolicyLayer and add a rule for timetable.prepare_day_entry: 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 Tlc Portal. Nothing to install.
timetable.prepare_day_entry 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 timetable.prepare_day_entry 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 timetable.prepare_day_entry. 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.
timetable.prepare_day_entry is provided by the Tlc Portal MCP server (mingovvv/tlc-portal-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 →