AI agents call mass_get_property 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.
This tool performs a query operation that retrieves data from multiple Roblox instances without creating, modifying, or deleting any content. It has no side effects and poses minimal risk even if misused by an AI agent, as it only exposes existing property values already accessible within Roblox Studio.
From the tool's definition Tool description states 'Read the same property from multiple instances at once' and returns an array of property values with no modification capability. The args are read-only (paths and propertyName), and the return type confirms retrieval only.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Read the same property from multiple instances at once. Args: - paths (string[]): Array of instance paths - propertyName (string): Property to read Returns: Array of { path, value } results. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.
Register the Melo MCP server in PolicyLayer and add a rule for mass_get_property: 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.
mass_get_property is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the mass_get_property 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 mass_get_property. 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.
mass_get_property 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.
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 →