roles

A execute tool on the iTerm MCP server.

SERVERiTerm MCP SOURCEresearch-developer/iterm-mcp-claude-agency

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/research-developer-iterm-mcp-claude-agency/roles.md

WHAT IT DOES

What roles does on iTerm MCP

AI agents invoke roles to trigger actions in iTerm MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why roles is rated High

Without a description, confidence is reduced. However, 'roles' on a terminal control server most likely manages role-based access control, which determines who can execute commands via the iTerm sessions. This makes it Execute-adjacent (controls what can be executed) rather than purely Read, though it could also be Write if it modifies role assignments.

From the tool's definition Tool named 'roles' with empty description on an iTerm MCP server that controls terminal sessions and command execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs roles safely

PolicyLayer is an MCP gateway: it sits between your AI agents and iTerm MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For roles, this is the rule to start with:

roles Rate-limited

roles stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "roles": {
      "limits": [
        {
          "counter": "roles_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect iTerm MCP, apply this rule, and every roles call is checked against it from then on.

FAQ

Questions about roles

What does the roles tool do? +

roles is a execute tool on the iTerm MCP server. It is categorised as a Execute tool in the iTerm MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on roles? +

Register the iTerm MCP server in PolicyLayer and add a rule for roles: 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 iTerm MCP. Nothing to install.

What risk level is roles? +

roles is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit roles? +

Yes. Add a rate_limit block to the roles 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 roles completely? +

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

roles is provided by the iTerm MCP server (research-developer/iterm-mcp-claude-agency). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on iTerm, and thousands of servers like it.

This server

All 16 iTerm tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →