Get a user's effective permission level on a repo (admin/write/read/none).
AI agents call get_repo_permission to retrieve information from Ghe Mcp Gateway 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 permission information (admin/write/read/none status) for a user on a repository. It is a read-only information retrieval operation with no side effects, no data modification, and no execution of external operations. The blast radius is minimal since it only exposes existing permission metadata. The server's read-only safety posture by default is consistent with this classification.
From the tool's definition Tool name 'get_repo_permission' and description 'Get a user's effective permission level on a repo' indicate a query operation that retrieves permission metadata without modifying any data.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get a user's effective permission level on a repo (admin/write/read/none). It is categorised as a Read tool in the Ghe Mcp Gateway MCP Server, which means it retrieves data without modifying state.
Register the Ghe Mcp Gateway MCP server in PolicyLayer and add a rule for get_repo_permission: 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 Ghe Mcp Gateway. Nothing to install.
get_repo_permission 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_repo_permission 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_repo_permission. 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_repo_permission is provided by the Ghe Mcp Gateway MCP server (mholzinger/ghe-mcp-gateway). 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 →