identity-group-read-by-name
AI agents call identity-group-read-by-name to retrieve information from Vault MCP Server (mschuchard) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about an identity group without modifying state. It is a data query operation with no side effects. The severity is low because reading identity group metadata poses minimal risk unless the group contains highly sensitive authorization data, but the operation itself is non-destructive and non-mutating.
From the tool's definition Tool name 'identity-group-read-by-name' indicates a read-only operation retrieving identity group information by name. No parameters or description provided suggest data modification.
Attacks that exploit this kind of access
identity-group-read-by-name. It is categorised as a Read tool in the Vault MCP Server (mschuchard) MCP Server, which means it retrieves data without modifying state.
Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for identity-group-read-by-name: 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.
identity-group-read-by-name 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 identity-group-read-by-name 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 identity-group-read-by-name. 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.
identity-group-read-by-name 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.
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 →