Return True if both strings appear in any common name cluster.
AI agents call share_cluster to retrieve information from Name Variants without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple read-only lookup operation that checks whether two name strings belong to the same cluster in a name romanization database. It returns a boolean result based on existing data with no side effects, data modification, code execution, or destructive operations.
From the tool's definition Tool is named 'share_cluster' and described as 'Return True if both strings appear in any common name cluster' — it queries and retrieves information (boolean match result) from a lookup structure without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Return True if both strings appear in any common name cluster. It is categorised as a Read tool in the Name Variants MCP Server, which means it retrieves data without modifying state.
Register the Name Variants MCP server in PolicyLayer and add a rule for share_cluster: 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 Name Variants. Nothing to install.
share_cluster 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 share_cluster 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 share_cluster. 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.
share_cluster is provided by the Name Variants MCP server (securityronin/name-variants). 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 →