Signal an action to the multi-instance coordination pool.
AI agents invoke pool_signal to trigger actions in MidOS - MCP Community Library. 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.
Signaling an action to a multi-instance coordination pool triggers external operations or state changes across potentially many running agent instances. This is not merely reading data — it actively dispatches or triggers behavior in the coordination system. The blast radius is high because a misused signal could affect multiple coordinated agent instances simultaneously.
From the tool's definition "Signal an action to the multi-instance coordination pool"
Attacks that exploit this kind of access
Signal an action to the multi-instance coordination pool. It is categorised as a Execute tool in the MidOS - MCP Community Library MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MidOS - MCP Community Library MCP server in PolicyLayer and add a rule for pool_signal: 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 MidOS - MCP Community Library. Nothing to install.
pool_signal 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 pool_signal 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 pool_signal. 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.
pool_signal is provided by the MidOS - MCP Community Library MCP server (midos-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 →