Return all active interview prep sessions.
AI agents call list_interviews_tool to retrieve information from Interview Prep without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns a list of interview preparation sessions. It performs no modifications, deletions, code execution, or financial transactions. It is a straightforward data retrieval operation, making it a Read category tool with low severity since exposing a list of active sessions carries minimal risk of misuse by an AI agent.
From the tool's definition Tool name 'list_interviews_tool' and description 'Return all active interview prep sessions' indicate a retrieval operation that queries existing data without modification or side effects.
Attacks that exploit this kind of access
Return all active interview prep sessions. It is categorised as a Read tool in the Interview Prep MCP Server, which means it retrieves data without modifying state.
Register the Interview Prep MCP server in PolicyLayer and add a rule for list_interviews_tool: 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 Interview Prep. Nothing to install.
list_interviews_tool 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 list_interviews_tool 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 list_interviews_tool. 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.
list_interviews_tool is provided by the Interview Prep MCP server (shenmali/interview-mcp-first). 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 →