gridstack_move_widget · GridStack MCP Server MCP

WHAT IT DOES

What gridstack_move_widget does on GridStack MCP Server

AI agents use gridstack_move_widget 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_move_widget needs a policy

The tool modifies widget position attributes within a dashboard layout, which is a reversible change to UI state data. It does not execute arbitrary code, delete data irreversibly, move money, or trigger external side effects beyond layout repositioning. The impact is localized to the dashboard layout state and can be easily undone by moving the widget to a different position.

From the tool's definition Tool name 'gridstack_move_widget' and description 'Move a widget to a new position' indicate modification of widget positioning data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gridstack_move_widget Rate-limited

gridstack_move_widget 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_move_widget": {
      "limits": [
        {
          "counter": "gridstack_move_widget_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_move_widget

What does the gridstack_move_widget tool do? +

Move a widget to a new position. 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_move_widget? +

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

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

Can I rate-limit gridstack_move_widget? +

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

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

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