Low Risk

list_running_projects

List all currently running Solar2D Simulator projects tracked by this server.

How to control list_running_projects ↓

What list_running_projects does on Solar2D MCP Server

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

Low Risk

Why list_running_projects needs a policy

This tool retrieves a list of running projects—a read-only query with no ability to modify, delete, or execute code. The blast radius of misuse is minimal; an attacker could only discover which projects are active, not interact with them or cause damage. Confidence is high due to clear evidence of read-only semantics.

From the tool's definition Tool name 'list_running_projects' and description 'List all currently running Solar2D Simulator projects tracked by this server' indicate a query operation that retrieves information without modification or side effects.

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

How to control list_running_projects

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

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

list_running_projects 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 Solar2D MCP Server — 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 list_running_projects

What does the list_running_projects tool do? +

List all currently running Solar2D Simulator projects tracked by this server. It is categorised as a Read tool in the Solar2D MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_running_projects? +

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

What risk level is list_running_projects? +

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

Can I rate-limit list_running_projects? +

Yes. Add a rate_limit block to the list_running_projects 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 list_running_projects completely? +

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

list_running_projects is provided by the Solar2D MCP Server MCP server (sensiblecoder/solar2d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Solar2D MCP Server tool call.

Start from Solar2D MCP Server, 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.

22 Solar2D MCP Server 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.