AI agents invoke services 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.
Given the server's documented purpose of enabling 'parallel command execution' and the presence of orchestration/delegation tools, 'services' likely manages or triggers services/operations within the terminal environment. This represents Execute risk: it probably triggers external operations or system services whose effects depend on arguments.
From the tool's definition Tool named 'services' on an iTerm MCP server that 'Controls iTerm2 terminal sessions' and enables 'command execution'. The sibling tools (agents, orchestrate, delegate) and server description establish this as an execution and orchestration platform.
Attacks that exploit this kind of access
services. 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.
Register the iTerm MCP server in PolicyLayer and add a rule for services: 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.
services is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the services 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 services. 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.
services 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.
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 →