Get a project user membership by username.
AI agents call get_project_user_by_username to retrieve information from Infisical MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing project user membership information based on a username parameter. It performs a read-only lookup operation with no side effects, no data modification, and no irreversible actions.
From the tool's definition Tool name 'get_project_user_by_username' and description 'Get a project user membership by username' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get a project user membership by username. It is categorised as a Read tool in the Infisical MCP MCP Server, which means it retrieves data without modifying state.
Register the Infisical MCP server in PolicyLayer and add a rule for get_project_user_by_username: 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 Infisical MCP. Nothing to install.
get_project_user_by_username 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 get_project_user_by_username 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 get_project_user_by_username. 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.
get_project_user_by_username is provided by the Infisical MCP server (plgonzalezrx8/infisicalmcp). 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 →