# set_property

A write tool on the Adr Fpga Bootstrap MCP server.

Agent View of the PolicyLayer registry record for `set_property`. HTML page: https://policylayer.com/tools/adr-fpga-bootstrap/set-property

## Facts

- Tool: `set_property`
- Server: Adr Fpga Bootstrap (`zxyyz/adr-fpga-bootstrap`) — https://policylayer.com/tools/adr-fpga-bootstrap.md
- Homepage: https://github.com/zxyyz/adr-fpga-bootstrap
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "set_property",
    "arguments": {}
  }
}
```

## Why set_property is rated Medium

The 'set_property' tool modifies object properties in the Godot editor—a write operation that is reversible (properties can be changed back). Although the description is uninformative, context from the server's purpose (Godot Engine editor control) and sibling tools strongly suggests this creates or modifies editor/scene state.

From the tool's own definition: "Tool is named 'set_property' on a Godot editor control server; sibling tools include 'create_object', 'create_script', 'delete_object', and 'editor_action', indicating this modifies engine state."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adr Fpga Bootstrap:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_property": {
      "limits": [
        {
          "counter": "set_property_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Adr Fpga Bootstrap (38)

- `job_cancel` — Destructive — https://policylayer.com/tools/adr-fpga-bootstrap/job-cancel.md
- `sources_remove` — Destructive — https://policylayer.com/tools/adr-fpga-bootstrap/sources-remove.md
- `build` — Execute — https://policylayer.com/tools/adr-fpga-bootstrap/build.md
- `messages` — Other — https://policylayer.com/tools/adr-fpga-bootstrap/messages.md
- `file_read` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/file-read.md
- `host_status` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/host-status.md
- `job_artifacts` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/job-artifacts.md
- `job_list` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/job-list.md
- `job_status` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/job-status.md
- `sources_list` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/sources-list.md
- `sync_status` — Read — https://policylayer.com/tools/adr-fpga-bootstrap/sync-status.md
- `add_include_dirs` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/add-include-dirs.md
- `agent_ensure` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/agent-ensure.md
- `file_grep` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/file-grep.md
- `ip_create` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-create.md
- `ip_generate` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-generate.md
- `ip_upgrade` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/ip-upgrade.md
- `job_events` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/job-events.md
- `job_logs` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/job-logs.md
- `project_close` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-close.md
- `project_info` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-info.md
- `project_open` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-open.md
- `project_unlock` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/project-unlock.md
- `report_cdc` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-cdc.md
- `report_clocks` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-clocks.md
- `report_diff` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-diff.md
- `report_drc` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-drc.md
- `report_methodology` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-methodology.md
- `report_power` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-power.md
- `report_timing_paths` — Write — https://policylayer.com/tools/adr-fpga-bootstrap/report-timing-paths.md
- …and 8 more: https://policylayer.com/tools/adr-fpga-bootstrap.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adr-fpga-bootstrap · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adr-fpga-bootstrap