gridstack_enable · GridStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What gridstack_enable does on GridStack MCP Server

AI agents use gridstack_enable to create or update resources in GridStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GridStack MCP Server environment.

WHY IT NEEDS A POLICY

Why gridstack_enable needs a policy

Enabling/disabling a grid modifies its operational state but does not irreversibly delete data or execute arbitrary code. This is a stateful modification (Write category). Severity is medium because disabling a grid could interfere with dashboard functionality and user workflows, but the change is reversible by re-enabling it. Confidence is 0.85 due to the description being brief but clear in intent.

From the tool's definition Tool name is 'gridstack_enable' with description 'Enable or disable the grid' — toggles grid state, which is a reversible configuration change that modifies the active state of the GridStack instance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gridstack_enable Rate-limited

gridstack_enable stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gridstack_enable": {
      "limits": [
        {
          "counter": "gridstack_enable_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about gridstack_enable

What does the gridstack_enable tool do? +

Enable or disable the grid. It is categorised as a Write tool in the GridStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gridstack_enable? +

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

What risk level is gridstack_enable? +

gridstack_enable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gridstack_enable? +

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

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

gridstack_enable is provided by the GridStack MCP Server MCP server (raghavsharma-simpplr/gridstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.