update_project_permissions · TestRail MCP Server MCP

WHAT IT DOES

What update_project_permissions does on TestRail MCP Server

AI agents use update_project_permissions to create or update resources in TestRail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TestRail MCP Server environment.

WHY IT NEEDS A POLICY

Why update_project_permissions needs a policy

This tool modifies project-level permission settings, which affects who can access and interact with TestRail projects. While reversible (can be changed again), unauthorized permission changes could grant inappropriate access or restrict legitimate users, making this a high-severity Write operation.

From the tool's definition Tool name 'update_project_permissions' and description 'Update project permissions' indicate modification of access control data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_permissions Rate-limited

update_project_permissions stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_project_permissions": {
      "limits": [
        {
          "counter": "update_project_permissions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TestRail MCP Server, so you can run agents against it safely.

FAQ

Questions about update_project_permissions

What does the update_project_permissions tool do? +

Update project permissions. It is categorised as a Write tool in the TestRail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_project_permissions? +

Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_project_permissions? +

update_project_permissions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_project_permissions? +

Yes. Add a rate_limit block to the update_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.

How do I block update_project_permissions completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_project_permissions? +

update_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.