Simulate a tap/click in the Solar2D simulator. Specify a bounding box using percentages and the tool taps the center. Example: a button spanning 30-50% horizontally and 60-70% vertically would use left=30, right=50, top=60, bottom=70.
AI agents invoke simulate_tap 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 triggers external operations (simulated touch/click events) in a running Solar2D simulator. The effects depend on the arguments (coordinates) and can cause arbitrary in-simulator actions such as button presses, UI interactions, or game state changes. This qualifies as Execute since it runs simulator interactions with side effects dependent on input parameters.
From the tool's definition Simulate a tap/click in the Solar2D simulator
Documented attack patterns abuse exactly the kind of access simulate_tap 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 simulate_tap:
{
"version": "1",
"default": "deny",
"tools": {
"simulate_tap": {
"limits": [
{
"counter": "simulate_tap_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}simulate_tap 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.
Simulate a tap/click in the Solar2D simulator. Specify a bounding box using percentages and the tool taps the center. Example: a button spanning 30-50% horizontally and 60-70% vertically would use left=30, right=50, top=60, bottom=70. 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 simulate_tap: 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.
simulate_tap 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 simulate_tap 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 simulate_tap. 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.
simulate_tap 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.