add_timesheets
AI agents use add_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.
Timesheets typically record work hours and project time allocation—reversible data that can be edited or deleted later. This is Write rather than Destructive. The blast radius is medium: misconfigured timesheets could misrepresent project costs, labor allocation, or billing, but the operation is not irreversible and does not involve direct financial transactions.
From the tool's definition Tool name 'add_timesheets' indicates creation or modification of timesheet records. The empty description prevents certainty, but 'add' is a Write operation pattern consistent with sibling tools like 'create_bug', 'create_story_or_task', and 'create_comments'…
Attacks that exploit this kind of access
add_timesheets. 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 add_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.
add_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 add_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 add_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.
add_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 →