gridstack_set_responsive · GridStack MCP Server MCP

WHAT IT DOES

What gridstack_set_responsive does on GridStack MCP Server

AI agents use gridstack_set_responsive 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_set_responsive needs a policy

This tool creates or modifies grid layout configuration (responsive breakpoint settings) in a reversible manner. It does not execute arbitrary code, delete data, or cause financial impact. The changes are configuration-level and can be undone by setting different breakpoints. This is typical Write category behavior for dashboard/layout tools.

From the tool's definition gridstack_set_responsive configures responsive breakpoints, which modifies grid layout configuration settings. The tool name indicates a 'set' operation that persists breakpoint configuration changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gridstack_set_responsive Rate-limited

gridstack_set_responsive 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_set_responsive": {
      "limits": [
        {
          "counter": "gridstack_set_responsive_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_set_responsive

What does the gridstack_set_responsive tool do? +

Configure responsive breakpoints. 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_set_responsive? +

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

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

Can I rate-limit gridstack_set_responsive? +

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

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

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