end_task
结束 begin_task 开启的区间，返回本次任务复盘：实际用时、调用次数、被限流次数、原定串行用时、以及按给定并发度第几轮会触顶。
This record as markdown: /tools/429-throttle-mcp/end-task.md
What end_task does on 429 Throttle
AI agents call end_task to retrieve information from 429 Throttle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why end_task is rated Low
Even though end_task only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs end_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 429 Throttle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For end_task, this is the rule to start with:
end_task is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 429 Throttle, apply this rule, and every end_task call is checked against it from then on.
Questions about end_task
结束 begin_task 开启的区间，返回本次任务复盘：实际用时、调用次数、被限流次数、原定串行用时、以及按给定并发度第几轮会触顶。. It is categorised as a Read tool in the 429 Throttle MCP Server, which means it retrieves data without modifying state.
Register the 429 Throttle MCP server in PolicyLayer and add a rule for end_task: 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 429 Throttle. Nothing to install.
end_task is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the end_task 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 end_task. 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.
end_task is provided by the 429 Throttle MCP server (429-throttle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 429 Throttle, and thousands of servers like it.
This server
Across the catalogue