Return previously generated questions for an interview.
AI agents call list_questions_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 previously generated interview questions—a pure read operation with no capability to modify, delete, execute code, or affect financial systems. The blast radius of misuse is minimal, as an agent can only access historical question data. Confidence is high due to clear retrieval semantics.
From the tool's definition Tool name 'list_questions_tool' and description 'Return previously generated questions for an interview' indicate retrieval of existing data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Return previously generated questions for an interview. 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_questions_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_questions_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_questions_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_questions_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_questions_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 →