get_connected_instances

Returns instances connected to the given one through known Instance-valued properties (Part0/Part1, Attachment0/1, Adornee, ObjectValue.Value, PrimaryPart, etc.). Args: - path (string): Source instance - direction (enum

Server Melo yannyhl/linkedsword-mcp
Category Read
Risk class Low
Parameters 00 required

What get_connected_instances does on Melo

AI agents call get_connected_instances to retrieve information from Melo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_connected_instances needs a policy

This tool queries and retrieves data about instance relationships within Roblox Studio without modifying any state, executing code, or triggering external operations. It is a pure read operation that traverses property relationships to enumerate connected instances. The blast radius of misuse is minimal—an agent could only discover instance connectivity information, which has no destructive or financial impact.

From the tool's definition Tool name is 'get_connected_instances' and description states it 'Returns instances connected to the given one through known Instance-valued properties'.

Questions about get_connected_instances

What does the get_connected_instances tool do? +

Returns instances connected to the given one through known Instance-valued properties (Part0/Part1, Attachment0/1, Adornee, ObjectValue.Value, PrimaryPart, etc.). Args: - path (string): Source instance - direction (enum. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_connected_instances? +

Register the Melo MCP server in PolicyLayer and add a rule for get_connected_instances: 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 Melo. Nothing to install.

What risk level is get_connected_instances? +

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

Can I rate-limit get_connected_instances? +

Yes. Add a rate_limit block to the get_connected_instances 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 get_connected_instances completely? +

Set action: deny in the PolicyLayer policy for get_connected_instances. 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 get_connected_instances? +

get_connected_instances is provided by the Melo MCP server (yannyhl/linkedsword-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.