Trigger the start of the customer interview process.
AI agents invoke start_interview to trigger actions in CopilotMCP. 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 is Execute rather than Write because it triggers an external process whose effects depend on runtime arguments and state, not merely creating or modifying a data record. While it may collect customer data (a write operation), the primary function is to initiate a multi-step customer-facing workflow.
From the tool's definition The tool description states it will 'Trigger the start of the customer interview process.' The verb 'trigger' indicates the tool initiates an external operation with side effects—it launches a workflow involving customer interaction and data collection that…
Attacks that exploit this kind of access
Trigger the start of the customer interview process. It is categorised as a Execute tool in the CopilotMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Copilot MCP server in PolicyLayer and add a rule for start_interview: 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 CopilotMCP. Nothing to install.
start_interview 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 start_interview 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 start_interview. 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.
start_interview is provided by the Copilot MCP server (mehrshadshams/copilotmcp). 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 →