Run a Solar2D project in the simulator. Provide either a path to main.lua or a project directory.
AI agents invoke run_solar2d_project to trigger actions in Solar2D MCP Server. 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.
This tool executes code (Lua scripts) whose behavior depends entirely on the project contents provided as arguments. While the execution is confined to a simulator environment rather than the host system, it still represents code execution with potential side effects including resource consumption, network access (common in games), or unexpected behavior.
From the tool's definition Tool description states it 'Run[s] a Solar2D project in the simulator' - the verb 'run' indicates execution of code. Solar2D is a Lua-based game development framework, and executing a project means running arbitrary Lua code from the specified path.
Documented attack patterns abuse exactly the kind of access run_solar2d_project gives an agent:
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 run_solar2d_project:
{
"version": "1",
"default": "deny",
"tools": {
"run_solar2d_project": {
"limits": [
{
"counter": "run_solar2d_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_solar2d_project 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.
Run a Solar2D project in the simulator. Provide either a path to main.lua or a project directory. It is categorised as a Execute tool in the Solar2D MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Solar2D MCP Server MCP server in PolicyLayer and add a rule for run_solar2d_project: 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.
run_solar2d_project 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 run_solar2d_project 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 run_solar2d_project. 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.
run_solar2d_project 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.
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.