long-running-task
Simulates a long-running task with progress notifications
This record as markdown: /tools/frontmcp/long-running-task.md
What long-running-task does on Frontmcp
AI agents invoke long-running-task to trigger actions in Frontmcp. 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.
Why long-running-task is rated High
The tool executes a simulated long-running task, which involves running a process and emitting progress notifications. It appears to be a demonstration/simulation tool rather than one with real-world side effects, but it does 'execute' a process. Severity is low because it's described as a simulation. Confidence is moderate because the description is vague about what the task actually does.
From the tool's definition 'Simulates a long-running task with progress notifications'
Attacks that exploit this kind of access
The rule that runs long-running-task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For long-running-task, this is the rule to start with:
long-running-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.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every long-running-task call is checked against it from then on.
Questions about long-running-task
Simulates a long-running task with progress notifications. It is categorised as a Execute tool in the Frontmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Front MCP server in PolicyLayer and add a rule for long-running-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 Frontmcp. Nothing to install.
long-running-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-running-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-running-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-running-task is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue