set_task_estimate
AI agents use set_task_estimate to create or update resources in RTM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RTM MCP Server environment.
This tool modifies task properties (estimate/duration) but does not delete or irreversibly destroy data. It aligns with Write-category operations that create or modify data reversibly. Confidence is moderate (0.75) due to the empty description, but context from sibling tools and the 'set' verb strongly suggest non-destructive task mutation.
From the tool's definition Tool name 'set_task_estimate' and sibling tools like 'add_task', 'add_task_tags', 'complete_task' indicate task metadata modification. The empty description and 'set' prefix suggest updating a task field (time estimate) reversibly.
Attacks that exploit this kind of access
set_task_estimate. It is categorised as a Write tool in the RTM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RTM MCP Server MCP server in PolicyLayer and add a rule for set_task_estimate: 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 RTM MCP Server. Nothing to install.
set_task_estimate 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_task_estimate 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_task_estimate. 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_task_estimate is provided by the RTM MCP Server MCP server (ljadach/rtm-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 →