AI agents use update_list_name to create or update resources in Interview — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interview environment.
This tool creates or modifies data reversibly by renaming a list. It does not delete data (Destructive), execute code (Execute), or commit financial transactions (Financial). The modification is reversible—the list name can be changed again. Given the low blast radius of renaming a task list, severity is low.
From the tool's definition Tool description states 'Cambiar, actualizar o update el nombre' (change, update the name), which is a modification operation. The tool updates/modifies an existing list name from 'OldName' to 'NewName'.
Attacks that exploit this kind of access
Cambiar, actualizar o update el nombre de la lista ‘OldName’ a o por 'NewName'. It is categorised as a Write tool in the Interview MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interview MCP server in PolicyLayer and add a rule for update_list_name: 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. Nothing to install.
update_list_name 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 update_list_name 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 update_list_name. 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.
update_list_name is provided by the Interview MCP server (matilarrazabal/mcp-server-interview). 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 →