AI agents call subscribe to retrieve information from tmux-claude MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Subscribing to messages is a read/monitoring operation that listens for data matching a pattern without creating, modifying, or deleting anything. In the context of a tmux/Claude orchestration server, this likely sets up a listener for inter-instance communication. The main risk is information exposure (reading messages from other Claude instances), but there are no write or execute side effects implied.
From the tool's definition Subscribe to messages matching a pattern
Documented attack patterns abuse exactly the kind of access subscribe gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and tmux-claude MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for subscribe:
{
"version": "1",
"default": "deny",
"tools": {
"subscribe": {}
}
}subscribe is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Subscribe to messages matching a pattern. It is categorised as a Read tool in the tmux-claude MCP Server MCP Server, which means it retrieves data without modifying state.
Register the tmux-claude MCP Server MCP server in PolicyLayer and add a rule for subscribe: 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 tmux-claude MCP Server. Nothing to install.
subscribe 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 subscribe 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 subscribe. 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.
subscribe is provided by the tmux-claude MCP Server MCP server (michael-abdo/tmux-claude-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from tmux-claude MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 tmux-claude MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.