更新花费工时,返回花费工时更新后的数据,每次只允许更新一条数据
AI agents use update_timesheets to create or update resources in TAPD MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TAPD MCP Server environment.
This tool modifies timesheet data reversibly. Updating timesheets is a Write operation as it changes existing records without permanently destroying them. Severity is medium because misuse could alter project time tracking, affecting resource allocation and billing accuracy, but the impact is limited to a single record per operation and is potentially correctable.
From the tool's definition Tool name 'update_timesheets' and description '更新花费工时' (update time/effort spent) indicates modification of timesheet records. The phrase '每次只允许更新一条数据' (only one record can be updated at a time) confirms this performs updates rather than deletions.
Attacks that exploit this kind of access
更新花费工时,返回花费工时更新后的数据,每次只允许更新一条数据. It is categorised as a Write tool in the TAPD MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TAPD MCP Server MCP server in PolicyLayer and add a rule for update_timesheets: 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 TAPD MCP Server. Nothing to install.
update_timesheets 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 update_timesheets 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 update_timesheets. 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.
update_timesheets is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). 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 →