remote-spy
WRITES LIVE GAME STATE. Controls the selected spy: lifecycle, configure, pause/resume, clear, block/unblock, ignore/unignore, and reset-controls. Select engine=cobalt (default) or ketamine. status reports effective capture/GUI settings and capabilities; controls lists active block/ignore rules wi...
This record as markdown: /tools/executor-mcp-roblox/remote-spy.md
What remote-spy does on Executor Mcp Roblox
AI agents call remote-spy to permanently remove resources in Executor Mcp Roblox, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remote-spy is rated Critical
An AI agent that decides to call remote-spy doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Executor Mcp Roblox is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs remote-spy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Executor Mcp Roblox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remote-spy, this is the rule to start with:
remote-spy is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Executor Mcp Roblox, apply this rule, and every remote-spy call is checked against it from then on.
Questions about remote-spy
WRITES LIVE GAME STATE. Controls the selected spy: lifecycle, configure, pause/resume, clear, block/unblock, ignore/unignore, and reset-controls. Select engine=cobalt (default) or ketamine. status reports effective capture/GUI settings and capabilities; controls lists active block/ignore rules with limit/offset and direction filters. reset-controls clears block/ignore rules in the selected direction, preserving history and capture settings; Ketamine GUI ignore rules span Both and reset only with direction=Both. logs/list support query filters; code generates call code without replay. Configuration is a patch; capture filters affect future MCP records only. Pausing recording preserves blocking and GUI logging. Starting another engine stops the previous after preflight; read/configuration operations never load spies. Block/ignore require observed remotes. Ketamine cannot block incoming RemoteEvents. restart expires IDs/views and resets configuration; stop unloads the selected GUI/hooks. It is categorised as a Destructive tool in the Executor Mcp Roblox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Executor Mcp Roblox MCP server in PolicyLayer and add a rule for remote-spy: 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 Executor Mcp Roblox. Nothing to install.
remote-spy is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remote-spy 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.
Set action: deny in the PolicyLayer policy for remote-spy. 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.
remote-spy is provided by the Executor Mcp Roblox MCP server (okenjioxx/executor-mcp-roblox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Executor Mcp Roblox, and thousands of servers like it.
Across the catalogue