AI agents invoke ask_message to trigger actions in Iris 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.
This tool sends a message to another team/project and awaits a response, triggering external operations across project boundaries. It's more than a simple read (it initiates communication and causes side effects in other systems) but not purely destructive or financial. The 'wait for response' aspect implies it blocks and coordinates with external agents, making Execute the most appropriate category.
From the tool's definition Ask a question to a team and wait for their response — triggers cross-project messaging and coordination with external Claude Code instances
Attacks that exploit this kind of access
Ask a question to a team and wait for their response. It is categorised as a Execute tool in the Iris MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iris MCP server in PolicyLayer and add a rule for ask_message: 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 Iris MCP. Nothing to install.
ask_message 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 ask_message 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 ask_message. 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.
ask_message is provided by the Iris MCP server (jenova-marie/iris-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 →