Get project permissions
AI agents call get_project_permissions to retrieve information from TestRail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves permission metadata for a project. It queries and returns data without side effects, making it a Read category tool. The low severity reflects that reading permissions alone poses minimal risk—it's informational and cannot modify system state or trigger actions. Confidence is high because the name and description clearly indicate a read-only retrieval operation.
From the tool's definition Tool name 'get_project_permissions' and description 'Get project permissions' indicate a retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get project permissions. It is categorised as a Read tool in the TestRail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for get_project_permissions: 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 TestRail MCP Server. Nothing to install.
get_project_permissions 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_permissions 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_permissions. 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_permissions is provided by the TestRail MCP Server MCP server (samuelvinay91/testrail-mcp). 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 →