Ask user to clarify their intent when the request is ambiguous or could be interpreted multiple ways
AI agents call clarify_intent to retrieve information from MCP-Confirm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool serves a purely informational purpose: gathering clarification from the user about their intent. It has no side effects, creates no data persistence, executes no code, and triggers no external operations. It is strictly a read/query operation retrieving user intent through confirmation protocols.
From the tool's definition Tool 'clarify_intent' asks users to clarify ambiguous requests—it only retrieves user input/intent through a question dialog, with no data modification, deletion, or execution of external actions.
Attacks that exploit this kind of access
Ask user to clarify their intent when the request is ambiguous or could be interpreted multiple ways. It is categorised as a Read tool in the MCP-Confirm MCP Server, which means it retrieves data without modifying state.
Register the MCP-Confirm MCP server in PolicyLayer and add a rule for clarify_intent: 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 MCP-Confirm. Nothing to install.
clarify_intent 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 clarify_intent 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 clarify_intent. 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.
clarify_intent is provided by the MCP-Confirm MCP server (mako10k/mcp-confirm). 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 →