Structural diff of two instance subtrees. Compares a curated set of properties plus child-by-name matching. Args: - pathA (string): First instance - pathB (string): Second instance - includeChildren (bool, default true): Recurse into children - propertyFilter (string[], optional): Restrict to the...
AI agents call compare_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.
This tool only reads and compares two instance subtrees, returning differences without modifying any data. It is a pure read/query operation with no side effects.
From the tool's definition Structural diff of two instance subtrees. Compares a curated set of properties plus child-by-name matching.
Attacks that exploit this kind of access
Structural diff of two instance subtrees. Compares a curated set of properties plus child-by-name matching. Args: - pathA (string): First instance - pathB (string): Second instance - includeChildren (bool, default true): Recurse into children - propertyFilter (string[], optional): Restrict to these properties Returns: { propertyDiffs[], childrenOnlyInA[], childrenOnlyInB[], countA, countB }. 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 compare_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.
compare_instances 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 compare_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.
Set action: deny in the PolicyLayer policy for compare_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.
compare_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.
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 →