Get a list of your identities/personas from PostIdentity
AI agents call list_identities to retrieve information from PostIdentity MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of existing identities/personas. It performs no modifications, deletions, code execution, or financial operations. It is a straightforward data retrieval action, fitting the 'Read' category. Severity is low because listing identities poses minimal risk—no destructive or operational actions can be triggered through this read-only operation.
From the tool's definition Tool name 'list_identities' and description 'Get a list of your identities/personas from PostIdentity' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get a list of your identities/personas from PostIdentity. It is categorised as a Read tool in the PostIdentity MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostIdentity MCP Server MCP server in PolicyLayer and add a rule for list_identities: 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 PostIdentity MCP Server. Nothing to install.
list_identities 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 list_identities 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 list_identities. 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.
list_identities is provided by the PostIdentity MCP Server MCP server (postidentity/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 →