obj_set_grid

Set the snap grid and/or visible grid size for the active schematic.

SERVEREda Agent SOURCEsalitronic/eda-agent

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eda-agent/obj-set-grid.md

WHAT IT DOES

What obj_set_grid does on Eda Agent

AI agents use obj_set_grid to create or update resources in Eda Agent, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eda Agent environment.

RISK

Why obj_set_grid is rated Medium

This tool changes design environment parameters (grid settings) which affects the schematic workspace state. While reversible and not destructive, it constitutes a Write operation as it modifies persisted or semi-persisted design configuration.

From the tool's definition Tool description states 'Set the snap grid and/or visible grid size' - this modifies grid settings in the active schematic, which is a reversible configuration change to the design environment.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs obj_set_grid safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Eda Agent, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For obj_set_grid, this is the rule to start with:

obj_set_grid Rate-limited

obj_set_grid 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": {
    "obj_set_grid": {
      "limits": [
        {
          "counter": "obj_set_grid_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Eda Agent, apply this rule, and every obj_set_grid call is checked against it from then on.

FAQ

Questions about obj_set_grid

What does the obj_set_grid tool do? +

Set the snap grid and/or visible grid size for the active schematic. It is categorised as a Write tool in the Eda Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on obj_set_grid? +

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

What risk level is obj_set_grid? +

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

Can I rate-limit obj_set_grid? +

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

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

obj_set_grid is provided by the Eda Agent MCP server (salitronic/eda-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Eda Agent, and thousands of servers like it.

This server

All 345 Eda Agent tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →