Set the active model (persists to config). Requires the matching API key.
AI agents use set_model_tool to create or update resources in Interview Prep — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interview Prep environment.
This tool creates or modifies application configuration data (the active model setting). While the change persists to config, it is reversible — the user can call set_model_tool again with a different model. This makes it Write rather than Destructive.
From the tool's definition Tool description states 'Set the active model (persists to config)' — this modifies configuration state persistently. The tool changes which AI model is active for the interview preparation server, which is a reversible configuration change.
Attacks that exploit this kind of access
Set the active model (persists to config). Requires the matching API key. It is categorised as a Write tool in the Interview Prep MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interview Prep MCP server in PolicyLayer and add a rule for set_model_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.
set_model_tool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_model_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 set_model_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.
set_model_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 →