identity-entities-merge · Vault MCP Server (mschuchard) MCP

WHAT IT DOES

What identity-entities-merge does on Vault MCP Server (mschuchard)

AI agents use identity-entities-merge to create or update resources in Vault MCP Server (mschuchard) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vault MCP Server (mschuchard) environment.

WHY IT NEEDS A POLICY

Why identity-entities-merge needs a policy

This tool modifies Vault's identity store by merging entities, which changes metadata, policies, and configurations associated with those identities. While not explicitly deleting data, the merge operation irreversibly consolidates identity records and could affect access control assignments.

From the tool's definition Tool name 'identity-entities-merge' indicates a merge operation on identity entities in Vault. The sibling tools (database-connection-delete, audit-device-disable, authentication-engine-disable) show this server manages destructive and state-changing…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

identity-entities-merge Rate-limited

identity-entities-merge stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "identity-entities-merge": {
      "limits": [
        {
          "counter": "identity-entities-merge_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vault MCP Server (mschuchard), so you can run agents against it safely.

FAQ

Questions about identity-entities-merge

What does the identity-entities-merge tool do? +

identity-entities-merge. It is categorised as a Write tool in the Vault MCP Server (mschuchard) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on identity-entities-merge? +

Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for identity-entities-merge: 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 Vault MCP Server (mschuchard). Nothing to install.

What risk level is identity-entities-merge? +

identity-entities-merge is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit identity-entities-merge? +

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

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

identity-entities-merge is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.