AI agents call get_project_users to retrieve information from Repsona 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 information about project members without modifying, deleting, or executing any operations. It is purely informational retrieval, fitting the Read category with low severity since disclosure of user membership lists has minimal security impact compared to other operations on this server.
From the tool's definition Tool name 'get_project_users' and description 'retrieves users participating in a specified project' (translated from Japanese: 指定したプロジェクトに参加しているユーザーを取得します) indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
指定したプロジェクトに参加しているユーザーを取得します. It is categorised as a Read tool in the Repsona MCP Server, which means it retrieves data without modifying state.
Register the Repsona MCP server in PolicyLayer and add a rule for get_project_users: 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 Repsona. Nothing to install.
get_project_users 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_users 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_users. 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_users is provided by the Repsona MCP server (@bellx2/repsona-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 →