AI agents use create_object to create or update resources in Melo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Melo environment.
This tool creates new instances/objects in Roblox's DataModel, which is a reversible modification operation. It does not execute arbitrary code, delete data, or move money, so it falls under Write. Severity is high because an AI agent could create malicious scripts, spawn performance-degrading instances, or pollute the project structure; however, these effects are generally recoverable through deletion or undo.
From the tool's definition Tool name 'create_object' and description 'Create a new instance in the DataModel' indicate creation of new data structures within Roblox Studio's object hierarchy.
Attacks that exploit this kind of access
Create a new instance in the DataModel. Args: - className (string): Roblox class to create (e.g. It is categorised as a Write tool in the Melo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Melo MCP server in PolicyLayer and add a rule for create_object: 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.
create_object is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_object 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 create_object. 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.
create_object 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 →