Simulate a long-running task with progress updates
AI agents invoke long_task to trigger actions in MCP TypeScript Starter. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool executes a simulated long-running task and emits progress updates, which constitutes running an operation/process. While 'simulate' suggests it may not have real-world side effects, the execution model (running a task with progress) places it firmly in the Execute category. Severity is medium because misuse could consume resources or time, but the simulated nature limits blast radius.
From the tool's definition Simulate a long-running task with progress updates
Documented attack patterns abuse exactly the kind of access long_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP TypeScript Starter, and nothing reaches the server without passing your rules. This is the rule we recommend for long_task:
{
"version": "1",
"default": "deny",
"tools": {
"long_task": {
"limits": [
{
"counter": "long_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}long_task stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Simulate a long-running task with progress updates. It is categorised as a Execute tool in the MCP TypeScript Starter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP TypeScript Starter MCP server in PolicyLayer and add a rule for long_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 MCP TypeScript Starter. Nothing to install.
long_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the long_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 long_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.
long_task is provided by the MCP TypeScript Starter MCP server (sammorrowdrums/mcp-typescript-starter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP TypeScript Starter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 MCP TypeScript Starter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.