long-running-task-with-message
Demonstrates a long running operation with progress updates and messages
This record as markdown: /tools/mcp-test-servers/long-running-task-with-message.md
What long-running-task-with-message does on Mcp Test Servers
AI agents invoke long-running-task-with-message to trigger actions in Mcp Test Servers. 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-with-message is rated High
The tool executes a long-running task, implying it performs some ongoing operation or computation. The description is vague about what the task actually does, but 'long running operation' implies execution of some process. Confidence is moderate because the description doesn't specify what the task does or its side effects.
From the tool's definition 'long running operation with progress updates and messages'
Attacks that exploit this kind of access
The rule that runs long-running-task-with-message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Test Servers, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For long-running-task-with-message, this is the rule to start with:
long-running-task-with-message 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 Mcp Test Servers, apply this rule, and every long-running-task-with-message call is checked against it from then on.
Questions about long-running-task-with-message
Demonstrates a long running operation with progress updates and messages. It is categorised as a Execute tool in the Mcp Test Servers MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Test Servers MCP server in PolicyLayer and add a rule for long-running-task-with-message: 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 Test Servers. Nothing to install.
long-running-task-with-message 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-with-message 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-with-message. 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-with-message is provided by the Mcp Test Servers MCP server (msfeldstein/mcp-test-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Test Servers, and thousands of servers like it.
Across the catalogue