Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Find hidden Remote / Bindable channels

find-hidden-remotes
Read-onlyIdempotent

Detect nil-parented or detached remote and bindable instances outside the game tree to expose hidden backdoor or data-exfiltration channels for inspection.

Instructions

Find RemoteEvent / RemoteFunction / UnreliableRemoteEvent / BindableEvent / BindableFunction instances that are NOT in the normal game tree — i.e. nil-parented or detached from the DataModel. A remote/bindable kept alive by a reference but hidden off the hierarchy is a classic backdoor / data-exfiltration channel: an exploit or malicious script fires it to phone home or to receive commands without the object ever appearing in the Explorer. This tool pulls getnilinstances() (the primary source of nil-parented objects) and, when getinstances() is available, also includes any remote/bindable that is not a descendant of game, deduping across both sources. It complements get-nil-instances / find-hidden-instances by narrowing to just the communication-channel classes and giving a ready-to-inspect list. Returns { count, byClass, truncated, samples: [{ class, name, location }] }, capped. Requires getnilinstances; getinstances is used additionally when present. Degrades with a clear error if neither is available. Signature: { limit: any?, maxScan: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Produces: bounded-candidates. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of detailed sample remotes/bindables to return in the samples list (default 200, clamped to 2000). The count and byClass tally always cover every hidden remote/bindable found regardless of this limit.
maxScanNoMax number of instances to examine from getinstances() before stopping the getinstances pass (default 60000, clamped to 500000). Protects against huge games; if hit, `truncated` is set true. The getnilinstances pass is always fully scanned.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the two data sources (getnilinstances plus optional getinstances), dedup across both, capping, the exact return shape, a hard dependency requirement, and graceful degradation with a clear error. That is rich behavioral disclosure beyond the annotation set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and threat rationale are front-loaded and every early sentence earns its place. The trailing metadata block (phase/cost/idempotency/requires/produces/safety/on-failure) is somewhat repetitive with the annotations and schema, slightly diluting conciseness, but the core is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description supplies the return shape ({ count, byClass, truncated, samples }), the dependency and degradation behavior, and the scoping rules. Combined with 100% parameter coverage, an agent has everything needed to call and interpret this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents limit, maxScan, and threadContext thoroughly (defaults, clamps, truncation semantics). The description adds only the generic note that output is 'capped' and does not add per-parameter meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (find) plus the exact resource classes (RemoteEvent/RemoteFunction/UnreliableRemoteEvent/BindableEvent/BindableFunction) and the defining scope condition (NOT in the normal game tree, nil-parented/detached). It also names the sibling tools it complements (get-nil-instances / find-hidden-instances) and how it narrows relative to them, so an agent can distinguish it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the investigative context ('classic backdoor / data-exfiltration channel') and explicitly positions itself as a narrower complement to get-nil-instances / find-hidden-instances, which implies when to pick it. It does not state an explicit when-not condition or a full alternative-selection rule, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools