Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Neutralize a function so it does nothing (MUTATES STATE via hookfunction)

block-function
Destructive

Installs a persistent no-op hook on a target Luau function to disable behaviors such as anticheat ticks or kick routines; stop restores the original.

Instructions

WRITES LIVE GAME STATE — INSTALLS A PERSISTENT GLOBAL HOOK. Replaces a target function with a no-op that ignores its arguments, returns nothing, and NEVER calls the original. Use this to disable a behavior outright: silence an anticheat heartbeat/tick, stop a function that kicks the player, neutralize a telemetry reporter, or freeze a damage routine. Distinct from spoof-function-return (which forces a specific return value) — block-function simply makes the call a complete no-op (returns nil/nothing). WORKFLOW (stateful — survives across tool calls via getgenv().__mcp_blockedFns, keyed by functionPath): 1. action='start' with functionPath — resolves the target, captures the original, installs the no-op stub. Returns { started, key }. 2. action='stop' with the same functionPath — restores the original function. Returns { stopped }. CAVEATS: the hook is GLOBAL and PERSISTS until you stop it (or the client restarts). Because the original never runs, blocking a function the game depends on can break gameplay, and a live function hook CAN TRIP ANTICHEAT. Always stop when done. Requires hookfunction, newcclosure, and getgenv; restoration uses hookfunction(target, original) with a restorefunction fallback. Returns { error } if a capability is missing, the target cannot be resolved, or there is already an active block for fetch/stop. Signature: { action: "start" | "stop", functionPath: string?, threadContext: number? }. Phase: act; cost=medium; idempotency=idempotent-write. Requires: active-client, resolved-target, explicit-mutation-approval. Produces: operation-receipt. Verify with: assert-state. Safety: MUTATING; writes live game/client state. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes'start' installs the no-op stub on functionPath; 'stop' restores the original function. Use the SAME functionPath for both so they address the same registry entry.
functionPathNoLuau expression resolving to the function to neutralize, e.g. 'getsenv(game.Players.LocalPlayer.PlayerScripts.AntiCheat).tick' or 'getconnections(game.Players.LocalPlayer.Idled)[1].Function'. Evaluated as `return <functionPath>` and must resolve to a function. REQUIRED for 'start'. For 'stop' it is the registry key identifying which block to restore, so it must match the string used at start.
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.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantial context beyond that: the hook is GLOBAL and persists until stopped or client restart, state lives in getgenv().__mcp_blockedFns keyed by functionPath, a live hook CAN TRIP ANTICHEAT, and required capabilities (hookfunction, newcclosure, getgenv) plus failure returns are disclosed. This is rich behavioral detail that the annotations alone do not convey.

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?

Front-loads the critical MUTATES STATE warning and the no-op contract before the workflow and caveats, which is well-structured. It is on the long side, with some meta-boilerplate (Phase/cost/idempotency line, 'Signature:' restatement, and a generic tool-schema pointer) that could be trimmed without loss.

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?

For a stateful, destructive mutation tool with no output schema, the description covers the required capabilities, the start/stop lifecycle, persistence and registry semantics, anticheat risk, and failure modes. An agent has everything needed to invoke it and to clean up correctly.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying the stateful relationship between the two actions — that 'stop' must address the same registry key created at 'start' — which is the key semantic hook for correct invocation.

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 ('Replaces a target function with a no-op'), the resource (a function), and the exact semantics (ignores arguments, returns nothing, never calls the original). It explicitly distinguishes itself from the sibling spoof-function-return, so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use scenarios (silence an anticheat heartbeat, stop a kick function, neutralize telemetry, freeze damage), names the alternative and the condition that selects it (spoof-function-return forces a value; block-function is a no-op), and lays out the full start/stop workflow with the requirement to use the same functionPath.

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