記録を再生(dryRunで事前確認、confirm=trueで実行)
AI agents invoke replayRecording to trigger actions in Roblox Studio Ultimate MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a pre-recorded sequence of actions within Roblox Studio. Although the description is in Japanese and somewhat terse ('記録を再生' = 'replay recording'), the dryRun and confirm parameters indicate it performs external operations whose effects depend on what was recorded and the arguments passed.
From the tool's definition Tool name 'replayRecording' combined with description indicating it replays a recording with dryRun preview and confirm execution mode.
Attacks that exploit this kind of access
記録を再生(dryRunで事前確認、confirm=trueで実行). It is categorised as a Execute tool in the Roblox Studio Ultimate MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Roblox Studio Ultimate MCP Server MCP server in PolicyLayer and add a rule for replayRecording: 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 Roblox Studio Ultimate MCP Server. Nothing to install.
replayRecording is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the replayRecording 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 replayRecording. 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.
replayRecording is provided by the Roblox Studio Ultimate MCP Server MCP server (jundayoo/roblox-studio-ultimate-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →