inspect-instance-metatable

Get metatable keys from a target Instance path (e.g., game.Players.LocalPlayer).

SERVERExecutor Mcp Roblox SOURCEokenjioxx/executor-mcp-roblox

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/executor-mcp-roblox/inspect-instance-metatable.md

WHAT IT DOES

What inspect-instance-metatable does on Executor Mcp Roblox

AI agents call inspect-instance-metatable to retrieve information from Executor Mcp Roblox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why inspect-instance-metatable is rated Low

Even though inspect-instance-metatable only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs inspect-instance-metatable 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 inspect-instance-metatable, this is the rule to start with:

inspect-instance-metatable Allowed

inspect-instance-metatable is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "inspect-instance-metatable": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Executor Mcp Roblox, apply this rule, and every inspect-instance-metatable call is checked against it from then on.

FAQ

Questions about inspect-instance-metatable

What does the inspect-instance-metatable tool do? +

Get metatable keys from a target Instance path (e.g., game.Players.LocalPlayer). It is categorised as a Read tool in the Executor Mcp Roblox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on inspect-instance-metatable? +

Register the Executor Mcp Roblox MCP server in PolicyLayer and add a rule for inspect-instance-metatable: 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.

What risk level is inspect-instance-metatable? +

inspect-instance-metatable is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit inspect-instance-metatable? +

Yes. Add a rate_limit block to the inspect-instance-metatable 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.

How do I block inspect-instance-metatable completely? +

Set action: deny in the PolicyLayer policy for inspect-instance-metatable. 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.

What MCP server provides inspect-instance-metatable? +

inspect-instance-metatable 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.

KEEP EXPLORING

More on Executor Mcp Roblox, and thousands of servers like it.

This server

All 291 Executor Mcp Roblox tools →

Across the catalogue

binary_inspect on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →