gridstack_column · GridStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What gridstack_column does on GridStack MCP Server

AI agents use gridstack_column 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_column needs a policy

The tool creates or modifies grid layout properties (column count) which affects the visual structure of dashboards. This is reversible and has limited blast radius—it reconfigures the layout system but doesn't destroy data, execute external code, or cause financial impact. Categorized as Write rather than Execute because it performs a specific configuration change without running arbitrary operations.

From the tool's definition Tool modifies layout configuration by changing the number of columns in a GridStack grid. This is a reversible state modification to grid properties, not data deletion or execution of arbitrary commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gridstack_column Rate-limited

gridstack_column 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_column": {
      "limits": [
        {
          "counter": "gridstack_column_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_column

What does the gridstack_column tool do? +

Change the number of columns. 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_column? +

Register the GridStack MCP Server MCP server in PolicyLayer and add a rule for gridstack_column: 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_column? +

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

Can I rate-limit gridstack_column? +

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

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

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