gridstack_margin · GridStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What gridstack_margin does on GridStack MCP Server

AI agents use gridstack_margin 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_margin needs a policy

This tool modifies grid margin and gap settings, which are visual layout properties. While reversible (margins can be changed back), it qualifies as Write rather than Read because it changes dashboard appearance and configuration. The severity is medium because misuse could degrade the UI/UX but has no data loss or financial impact.

From the tool's definition Tool name 'gridstack_margin' with description 'Update grid margin/gap' indicates modification of grid layout properties. The verb 'Update' explicitly signals a write operation that modifies existing configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gridstack_margin Rate-limited

gridstack_margin 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_margin": {
      "limits": [
        {
          "counter": "gridstack_margin_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_margin

What does the gridstack_margin tool do? +

Update grid margin/gap. 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_margin? +

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

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

Can I rate-limit gridstack_margin? +

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

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

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