Low Risk

get_running_tasks

Get all currently running tasks.

How to control get_running_tasks ↓

What get_running_tasks does on Prospectio MCP API

AI agents call get_running_tasks to retrieve information from Prospectio MCP API without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_running_tasks needs a policy

This tool retrieves status information about running tasks without creating, modifying, deleting, or executing anything. It is a read-only operation that queries task state, analogous to listing or fetching data. The blast radius of misuse is minimal—an attacker could gain visibility into system task status but cannot alter state or trigger actions.

From the tool's definition Tool name 'get_running_tasks' and description 'Get all currently running tasks' indicate a query/retrieval operation with no data modification or side effects.

Documented attack patterns abuse exactly the kind of access get_running_tasks gives an agent:

How to control get_running_tasks

PolicyLayer is an MCP gateway — it sits between your AI agents and Prospectio MCP API, and nothing reaches the server without passing your rules. This is the rule we recommend for get_running_tasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_running_tasks": {}
  }
}

get_running_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Prospectio MCP API — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_running_tasks

What does the get_running_tasks tool do? +

Get all currently running tasks. It is categorised as a Read tool in the Prospectio MCP API MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_running_tasks? +

Register the Prospectio MCP API MCP server in PolicyLayer and add a rule for get_running_tasks: 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 Prospectio MCP API. Nothing to install.

What risk level is get_running_tasks? +

get_running_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_running_tasks? +

Yes. Add a rate_limit block to the get_running_tasks 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.

How do I block get_running_tasks completely? +

Set action: deny in the PolicyLayer policy for get_running_tasks. 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.

What MCP server provides get_running_tasks? +

get_running_tasks is provided by the Prospectio MCP API MCP server (prospectio-ai/prospectio-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Prospectio MCP API tool call.

Start from Prospectio MCP API, 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.

12 Prospectio MCP API tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.