gd_shake_trigger · Geometry Dash Mcp Geode MCP

WHAT IT DOES

What gd_shake_trigger does on Geometry Dash Mcp Geode

AI agents invoke gd_shake_trigger to trigger actions in Geometry Dash Mcp Geode. 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 IT NEEDS A POLICY

Why gd_shake_trigger needs a policy

This tool executes a command that causes a side effect (camera shake) in a running game/level editor environment. While the effect is reversible and non-destructive, it constitutes triggering an external operation whose consequences depend on the arguments provided (placement, duration, intensity).

From the tool's definition Tool name 'gd_shake_trigger' and description 'Create a Shake Trigger to shake the camera' indicate it triggers an external operation (camera shake effect) within the Geometry Dash level editor whose visual/gameplay effects depend on when and how it is invoked.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gd_shake_trigger Rate-limited

gd_shake_trigger 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gd_shake_trigger": {
      "limits": [
        {
          "counter": "gd_shake_trigger_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Geometry Dash Mcp Geode, so you can run agents against it safely.

FAQ

Questions about gd_shake_trigger

What does the gd_shake_trigger tool do? +

Create a Shake Trigger to shake the camera. It is categorised as a Execute tool in the Geometry Dash Mcp Geode MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on gd_shake_trigger? +

Register the Geometry Dash Mcp Geode MCP server in PolicyLayer and add a rule for gd_shake_trigger: 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 Geometry Dash Mcp Geode. Nothing to install.

What risk level is gd_shake_trigger? +

gd_shake_trigger is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit gd_shake_trigger? +

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

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

gd_shake_trigger is provided by the Geometry Dash Mcp Geode MCP server (noame2289-afk/geometry-dash-mcp-geode). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.