# effect_probe

Verifica se uma acao no jogo produziu o efeito esperado.

Agent View of the PolicyLayer registry record for `effect_probe`. HTML page: https://policylayer.com/tools/mcp-godot-desenvolvimento/effect-probe

## Facts

- Tool: `effect_probe`
- Server: Mcp Godot Desenvolvimento (`joabcostamd/mcp-godot-desenvolvimento`) — https://policylayer.com/tools/mcp-godot-desenvolvimento.md
- Homepage: https://github.com/joabcostamd/mcp-godot-desenvolvimento
- 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": "effect_probe",
    "arguments": {}
  }
}
```

## Why effect_probe is rated Medium

An AI agent can call effect_probe faster than any human can review: one bad instruction and it creates or modifies resources in Mcp Godot Desenvolvimento by the hundred, each call as confident as the last.

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on Mcp Godot Desenvolvimento (291)

- `addon_delete_node` — Destructive — https://policylayer.com/tools/mcp-godot-desenvolvimento/addon-delete-node.md
- `delete_file` — Destructive — https://policylayer.com/tools/mcp-godot-desenvolvimento/delete-file.md
- `delete_node` — Destructive — https://policylayer.com/tools/mcp-godot-desenvolvimento/delete-node.md
- `detach_script` — Destructive — https://policylayer.com/tools/mcp-godot-desenvolvimento/detach-script.md
- `remove_background` — Destructive — https://policylayer.com/tools/mcp-godot-desenvolvimento/remove-background.md
- `build_csharp` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/build-csharp.md
- `build_export` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/build-export.md
- `compile_test` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/compile-test.md
- `deploy_itch` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/deploy-itch.md
- `execute_gdscript_runtime` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/execute-gdscript-runtime.md
- `game_performance` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/game-performance.md
- `godot_run_project` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/godot-run-project.md
- `godot_stop_project` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/godot-stop-project.md
- `godot_wait_for_bridge` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/godot-wait-for-bridge.md
- `launch_editor` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/launch-editor.md
- `run_game` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/run-game.md
- `run_gut_tests` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/run-gut-tests.md
- `run_scripted_tests` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/run-scripted-tests.md
- `run_stress_test` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/run-stress-test.md
- `run_verification_pipeline` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/run-verification-pipeline.md
- `smart_restart` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/smart-restart.md
- `start_recording` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/start-recording.md
- `stop_game` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/stop-game.md
- `stop_recording` — Execute — https://policylayer.com/tools/mcp-godot-desenvolvimento/stop-recording.md
- `addon_get_scene_tree` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/addon-get-scene-tree.md
- `addon_is_available` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/addon-is-available.md
- `addon_take_screenshot` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/addon-take-screenshot.md
- `analyze_game_structure` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/analyze-game-structure.md
- `analyze_signal_flow` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/analyze-signal-flow.md
- `auto_screenshot` — Read — https://policylayer.com/tools/mcp-godot-desenvolvimento/auto-screenshot.md
- …and 261 more: https://policylayer.com/tools/mcp-godot-desenvolvimento.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=mcp-godot-desenvolvimento · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/mcp-godot-desenvolvimento